Shareware Grab Bag

home *** CD-ROM | disk | FTP | other *** search

/ Shareware Grab Bag / Shareware Grab Bag.iso / 098 / rbs5bdoc.arc / RBBS-PC.DOC

Wrap

Text File | 1985-09-15 | 241.9 KB | 4,931 lines

REMOTE BULLETIN BOARD SYSTEM for the IBM Personal Computer Version CPC12.5 Copyright 1983, 1984, 1985 by D. Thomas Mack 10210 Oxfordshire Road Great Falls, Virginia 22066 VOICE -- (703) 759-4357 DATA #1 -- (703) 759-5049 #2 -- (703) 759-9659 AND Jon Martin 4396 N. Prairie Willow Ct. Concord, California 94521 DATA -- (415) 689-2090 Ken Goosens 5020 Portsmouth Road Fairfax, Virginia DATA -- (202) 537-7475 August 25, 1985 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 TABLE OF CONTENTS Page ----------------- ---- 1.0 INTRODUCTION 5 1.1 The Capital PC Users Group 5 1.2 The "contributions" requested for RBBS-PC 5 1.3 The "history" behind RBBS-PC 6 1.4 RBBS-PC Update Conventions 10 1.5 An Example of "Users Helping Users" 11 1.6 What's new with CPC12.5B 13 2.0 RBBS-PC "BASE-LINE" HARDWARE REQUIREMENTS 14 3.0 RBBS-PC's SUPPORT POLICIES 15 3.1 RBBS-PC's Vendor Support Policy 15 3.2 RBBS-PC's User Support Policy 18 4.0 OPERATING SYSTEM REQUIREMENTS 19 5.0 HOW TO GET A COPY OF RBBS-PC SENT TO YOU 19 6.0 FILES RBBS-PC USES 20 6.1 RBBS-PC System Files 21 6.2 RBBS-PC Text Files 23 7.0 USING THE "CONFIG" UTILITY TO CONFIGURE RBBS-PC CPC12 25 7.1 Global RBBS-PC Parameters (Part 1 of 2) 26 7.1.1 SYSOP's Name and Password for Remote Access 26 7.1.2 Password to Locally Take Over RBBS-PC as SYSOP 26 7.1.3 SYSOP's Default Sign-on Mode 26 7.1.4 SYSOP's "office" Hours 26 7.1.5 Use of Printer Bell 26 7.1.6 Number of Rings RBBS-PC Waits Before Answering 26 7.1.7 Drive Available for Uploading 27 7.1.8 Name of Directory to Update for Uploads 27 7.1.9 Drives Available for Downloading 27 7.1.10 Prompt Sounds 27 7.1.11 Maximum Time per Session 27 7.1.12 Limit Maximum Time on System Per Day 28 7.1.13 Months of Inactivity before a User is Deleted 28 7.1.14 Communication Port to be Used 28 7.1.15 Version of DOS RBBS-PC Will Run Under 28 7.1.16 Name of RBBS-PC 28 7.2 Global RBBS-PC Parameters (Part 2 of 2) 28 7.2.1 Color Monitor's Foreground/Background/Border 28 7.2.2 Selecting the Modem Speaker On or Off 29 7.2.3 Reminding Users of Messages They Left 29 7.2.4 Remind Users of Uploads and Downloads 29 7.2.5 Remind Users of Their Profile Preferences 29 7.2.6 Default User Page Length 29 7.2.7 Maximum Number of Lines per Message 29 7.2.8 Requiring non-ASCII Protocol for Binary Files 29 7.2.9 MICROCOM's MNP Protocol 29 7.2.10 Omitting First Level Directory in "New" Command 30 7.2.11 Omitting Upload Directory in "New" Command 30 7.2.12 Making System "Welcome" Interruptable 30 7.2.13 Making System Bulletins "Optional" 30 7.2.14 Is RBBS-PC running on a non-IBM PC? 30 7.2.15 Issuing Modem Commands Between Rings 31 7.2.16 Baud Rate to Initially Open Modem At 31 7.2.17 Seconds Waited Before Logging Off Idle Users 31 Page 2 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 TABLE OF CONTENTS (continued) Page ----------------------------- ---- 7.3 Parameters for RBBS-PC "text" Files 31 7.3.1 Drive Containing RBBS-PC "Bulletins" 31 7.3.2 Name of File Describing "Bulletins" 31 7.3.3 Number of System Bulletins 31 7.3.4 Prefix Used to Name Bulletin files 31 7.3.5 Drive Containing On-line Help Files 32 7.3.6 Prefix Used to Name Help Files 32 7.3.7 Name of "NEWUSER" File 32 7.3.8 Name of "WELCOME" File 32 7.3.9 Name of File Describing File Directories 32 7.3.10 Name of SYSOP's Command Menu 32 7.3.11 Name of Messages Subsystem Command Menu 32 7.3.12 Name of File Subsystem Command Menu 33 7.3.13 Name of Utilities Subsystem Command Menu 33 7.3.14 Menu that Lists Available Conferences 33 7.3.15 File Containing Invalid User Names 33 7.3.16 Factor to Extend Session Time for Uploads 34 7.3.17 Default System Type for New Users 34 7.4 Parameters for RBBS-PC "system" Files 34 7.4.1 Name of "MESSAGES" File 34 7.4.2 Name of "CALLERS" File 34 7.4.3 Name of File Containing "Comments" for the SYSOP 34 7.4.4 Name of "USERS" File 34 7.5 Parameters for RBBS-PC "Doors" 34 7.5.1 Enabling the "Door" Subsystem 34 7.5.2 Name of Menu that Lists the Available "Doors" 34 7.5.3 File RBBS Builds Dynamically to Open a "Door" 35 7.5.4 File to Re-invoke RBBS-PC When a "Door" Closes 35 7.6 Parameters for RBBS-PC's Security 35 7.6.1 Minimum Security Level to Get Into RBBS-PC 35 7.6.2 Default Security Level for New Callers 35 7.6.3 Default Security Level for SYSOP 35 7.6.4 File of File Names With Download Security 35 7.6.5 Minimum Security Level to See SYSOP's Menu 36 7.6.6 Minimum Security Level to Use RBBS-PC "Doors" 36 7.6.7 Maximum # of Security Violations Before Lockout 36 7.6.8 Security Level(s) for Each Command 36 7.6.9 File With Privileged Group Passwords 36 7.6.10 Maximum Number of Password Changes Per Session 36 7.6.11 Minimum Security For Temporary Password Changes 36 7.6.12 Minimum Security to Overwrite Files on Uploads 36 7.6.13 Security Level of Conference "Viewers" 36 7.6.14 Security Levels Exempt from Purge of User File 37 7.7 Parameters for Multiple RBBS-PC's/Conferences 37 7.7.1 Maximum Number of Concurrent RBBS-PC's 37 7.7.2 Environment Running Concurrent RBBS-PC's 37 7.7.3 Method RBBS-PC Uses to "Recycle" When User Logsoff 37 7.7.4 Maximum Number of Records in the "USERS" File 37 7.7.5 Maximum Number of Records in the "MESSAGES" File 38 7.7.6 Maximum Number of Messages Allowed 38 7.7.7 Conference File Maintenance 38 7.8 RBBS-PC SYSOP Utilities 38 7.8.1 Packing the "MESSAGES" File 38 7.8.2 Packing the "USERS" File 39 7.8.3 Printing Message Header Records 39 7.8.4 Renumbering Messages 39 7.8.5 Repairing the MESSAGES File 39 7.8.6 Initialize Hayes 2400 Firmware for RBBS-PC 39 Page 3 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 TABLE OF CONTENTS (continued) Page ----------------------------- ---- 8.0 THE HAYES MODEM SWITCH SETTINGS AND CONSIDERATIONS 40 9.0 COMMUNICATION BUFFER 41 10.0 USING MULTIPLE FILE DIRCTORIES 41 11.0 SETTING UP ".BAT" FILES FOR RBBS-PC 42 12.0 THE USE OF RBBS-PC "DOORS" 44 13.0 THE SECURITY FEATURES OF RBBS-PC 45 13.1 RBBS-PC's Security Features 45 13.2 Examples Using RBBS-PC's Security Features 46 13.3 How to Implement the Password File 47 13.4 How to Implement the Security for Download Files 48 13.5 How to Implement the Security for RBBS-PC Commands 49 13.6 Beware of the "Trojan Horse" 51 14.0 SYSOP FUNCTIONS 51 14.1 SYSOP Commands Within RBBS-PC 51 14.2 SYSOP's Use of Function Keys 53 15.0 DOS LIMITATIONS ON RUNNING PROGRAMS REMOTELY 54 15.1 How to Get DOS to Monitor Carrier Detect 54 15.2 How to Redirect Graphic Displays to Remote Users 55 16.0 CONFERENCING WITH RBBS-PC 55 17.0 UPLOADED FILE TIPS 57 18.0 COMPILING AND LINKING RBBS-PC 57 18.1 Compiling CONFIG.BAS and RBBS-PC.BAS 57 18.2 LINKing CONFIG 57 18.3 LINKing RBBS-PC Without MNP File Transfer Protocol 58 18.4 LINKing RBBS-PC With MNP File Transfer Protocol 58 19.0 LIMITED LICENSE 59 20.0 LIMITED WARRANTY 59 21.0 UPGRADING FROM CPC12-3B TO CPC12-5B 59 22.0 RBBS-PC FUTURE DIRECTIONS 60 APPENDICES: A -- RBBS-PC Record Formats 62 B -- RBBS-PC Vendor Protocol Interface Specifications 66 C -- RBBS-PC in a MultiLink Environment 67 D -- RBBS-PC in a CORVUS Network 69 E -- RBBS-PC in a ORCHID or AST PCnet Network 70 F -- RBBS-PC and the Hearing Impaired 72 G -- RBBS-PC and the IBM PCjr 73 H -- RBBS-PC Subscription Service 75 I -- RBBS-PC National Listing Service 76 J -- RBBS-PC and the Ark-Paradyne Modem Switch Settings 77 Page 4 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 1.0 INTRODUCTION ---------------- RBBS-PC is a Remote Bulletin Board System for the IBM personal computer, hence the name RBBS-PC. RBBS-PC has two fundamental purposes -- to be a catalyst for the free exchange of information, and to serve as an educational example of what can be done with BASIC. I distribute RBBS-PC under the trademark "Userware" because RBBS-PC is the sure and present proof that software which is shared becomes better than it was. RBBS-PC is the result of many thousands of man-hours of effort and is what it is today because of the many software contributions and suggestions by both members of the Capital PC Users Group and others. Everyone has something that they believe strongly in. For me it is the "Userware" concept and the free exchange of information. As John Naisbitt states in his book, MEGATRENDS, "...the new source of power is not money in the hands of a few, but information in the hands of the many." For this reason I have devoted the time I have in writing, maintaining, and enhancing RBBS-PC over the years. The reason that I am the registered copyright owner of RBBS-PC and grant the limited license that I do is to primarily insure that these purposes are not abrogated. 1.1 The Capital PC Users Group ------------------------------ Because the fundamental purposes of RBBS-PC and the Capital PC Users Group are similar, I package and forward each new version of RBBS-PC to the CPCUG's Software Exchange for distribution. The Capital PC User Group is a Maryland Corporation whose "legal name" is the Capital PC User Group Inc. The CPCUG is a non-profit organization according to Section 501C4, Social Welfare, of federal law. All revenues are re-invested in and applied to the CPCUG's education programs. 1.2 The "contributions" requested for RBBS-PC ---------------------------------------------- The "logo" of RBBS-PC requests contributions. This is because the RBBS-PC may be perceived as an advantage to user-groups, businesses, or government agencies. It is hard to put a value on the RBBS-PC as it varies from organization to organization and from time-frame to time-frame. The first and most desirable level of "contribution" is public domain software sent to the Capital PC Software Exchange (P.O. Box 6128, Silver Spring, MD 20906). This requires that you or your organization take the time and trouble to document whatever you wish to share. I would advise you to be prepared to convince your organization's legal department that IBM PC utilities, "peeks/pokes", etc. are sharable with the world in general. Often these are perceived as "proprietary" and lawyers tend to view software contributions to the "public domain" as the needless jeopar- dizing of your organization's technical dominance. This legal myopia over- looks the fact that "public domain" software can be used to establish your organization's technical dominance. If you have a new PC hardware product, "public domain" software that demonstrates it's potential may be just the marketing strategy to create a demand for the product. If you are a consulting organization, your technical reputation may be widely spread through "public domain" software. If you wish to contribute software but don't wish it to be "public domain," consider contributing it under a limited license similar to the one under which RBBS-PC is distributed (see section 19). Page 5 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 The next level of "contribution" is equipment or services. Be inventive in light of the CPCUG's objectives under 1.1. If you or your organization can donate equipment, software, supplies, or services to the CPCUG, feel free to do so. If you are so inclined, but before you do so, contact the Capital PC User Group, P.O. Box 3189, Gaithersburg, MD 20878. For general information about the appropriateness of the bequest, contact the Capital PC User Group directly. The last level of "contribution" is merely money. This is the one commo- dity that we are willing to exchange among each other without first having obtained the respect, consideration, etc. of the other party. It is per- haps the easiest to give as it exonerates us from the other levels of "contribution." CPCUG is an all volunteer organization and, of course, money is seldom plentiful. However the essence of CPCUG is the time, ideas, and effort that each of the volunteers contribute to it. For this reason, while money is always appreciated, money is not the best or even the second-best type of "contribution" you could make. Independent of whether you can donate public domain software, equipment, services, supplies, or money, consider becoming a member of CPCUG. If you wish to become a member of CPCUG, simply send your name, address, home/work phone numbers along with $25 to CPCUG, P.O. Box 3189, Gaithersburg, MD 20878. If in the final analysis you feel that you can do none of the above, o remember those who have, o enjoy what they have nurtured, and o keep the faith with those who have gone before you. 1.3 The "history" behind RBBS-PC -------------------------------- Electronic bulletin board systems have been around ever since personal computers existed. The first ones were very primitive and usually consisted of some posted notices and maybe allowed for on-line messages. It must be remembered that the IBM PC was only announced in August of 1981 and first became available in October of 1981. Therefore it is not supprising that the early history of BBS' is associated with non-IBM personal computers. The "early history" of bulletin board systems began around 1978 in Chicago with the CBBS/Chicago (Computerized Bulletin Board System/Chicago). It was created by Ward Christensen and Randy Suess -- members of the Chicago Area Computer Hobbyist Exchange (CACHE). CBBS for the CP/M is written in 8080 Assembler language (11,000 lines of it) and, like the early versions of RBBS-PC (i.e. prior to CPC12-5A), detects the baud rate and the parity of the user when he first signs on from the three carriage returns that the user must enter. About the same time, Bill Abney wrote a BBS for the Radio Shack TRS-80 Models I and II called Forum-80. The earliest BBS that I know of was written for the Apple (who else had personal computers in those days?) called the "Apple Bulletin Board System" (ABBS). It was written by Craig Vaughn and Bill Blue. They later created another bulletin board system for the Apple II called the People's Message System (PMS) Another Apple bulletin board system that came into being was for the Apple II, II+, and IIE as well as the Franklin Ace and it was called the Page 6 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 CommuniTree. It was written in the FORTH language and was authored by Dean Gengle and several others. When IBM announced it's first personal computer, the IBM PC, in August of 1981, there was no BBS' for it. In the summer of 1982, Brad Hanson found a prototype version written by Russ Lane in IBM's BASIC on the Dallas R/CPM\CBBS system. Brad added many fixes and modifications. In the first half of 1983, many members of the Capital PC Users Group's Communication Special Interest Group (SIG) such as Larry Jordan, Rich Schinnell, Gary Horwith, Jim Fry, Scot Loftesness, and Dorn Stickle further enhanced it and added XMODEM file transfer capability until it became known as RBBS-PC CPC 09 in May of 1983. At that time each feature or modification was identified by a new version number; it still ran only under the BASIC interperter; and was both relatively slow (because of the interperter) and somewhat unstable (it would normally "crash" at least once each day). Late in May of 1983, I asked Rich Schinnell if there were any "bulletin board" software available for the IBM PC written in BASIC. Rich told me to give Larry Jordan a call. Larry said that he was just getting CPC09 ready to send to Rich Schinnel who at that time was Director of the Capital PC User Group's Public Domain Software Library and that I could get it from Rich. I did, and still have the diskette just as Rich sent it to me -- dated June 22, 1983. Bulletin board systems, historically were the result of a single person or small group of person's efforts and tended to serve a very narrow interest group -- typically those interested in the medium itself (i.e. PC's, programming, communications, etc.). This was true up to and including RBBS-PC CPC09. In fact, most of the incentive to get the public domain versions of RBBS (CPC09 and earlier) functioning was to introduce the XMODEM protocol to the IBM PC-based community. In this CPC09 was successful and may have been the primary incentive for XMODEM to be included in PC-TALK at all. Since June of 1983 I have authored and released TWENTY-ONE versions of RBBS-PC and distributed them exclusively through the Capital PC User Group under the limited license described in section 19 of this documentation. At this time RBBS-PC appears to have become the "industry standard" for IBM-type personal computer bulletin board systems. However, even from the very beginning BBSs have excelled whenever: a.) there was a geographically dispersed audience, b.) with a need to exchange highly complex/technical information, c.) in a timely and accurate manner. RBBS-PC's impact has been to open an entirely new medium of communications between people. Rather than as an end in and of itself, RBBS-PC has come to serve as a means to an end -- the free exchange of ideas. On a technical level it is certainly an example that shows "real programmers can/do program in BASIC." I would like to think that RBBS-PC had something to do with IBM and Micorsoft coming out with new versions of the BASIC compiler that support communications, sub-routines, local and global variables, file-locking in a networking environment, etc. RBBS-PC represents a fundamental cornerstone, not just a phase, in what can be viewed as a "social rennasiance." The three areas that I mentioned earlier in which bulletin boards excel seem to ebb and flow within communities and organizations. RBBS-PC provides an almost instantaneous Page 7 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 mechanism by which these needs can be met. Many of the Big 8 accounting firms bring up RBBS-PC's just to fulfill one contract so that the various geographically disbursed members on the contract can communicate across time zones and continents. Unlike radio, newspapers, and television -- RBBS-PC provides a vehicle within which information can be EXCHANGED! That is what makes RBBS-PC so unique. Because the exchange is written, it is structured. Because it is structured, it can be thoughtfull. The "social renassiance" that RBBS-PC represents is the electronic elimination of those barriers that had previously inhibited the "exchange" of information within our society. RBBS-PC provides every personal computer owner with his own "soap-box" in a national Hyde Park. Previously the channels of communication had built-in barriers to "exchange," with RBBS-PC those barriers begin to cease to exist. While only the most fanatical RBBS-PC trivia experts may be interested, I've gone back and checked all the documentation and releases of RBBS-PC that I've authored and here is the tedious chronolgy: RBBS-PC Version Release Date of Major Enhancements Number First Version CPC10.0 07/04/83 RBBS-PC first written to be compilable by IBM's BASIC compiler, version 1.0 CPC11.0 08/10/83 RBBS-PC restructured so that all parameters were external (i.e. in the RBBS-PC.DEF) allowing SYSOP's who didn't want to spend the $300 for the BASIC compiler to tailor RBBS-PC to their taste. CONFIG.BAS was first written to generate RBBS-PC.DEF. CPC11.1 09/15/83 Jon Martin contributed UTSPACE.OBJ (a sub- routine that allowed the compiled version of RBBS-PC to determine the amount of free space available for uploading. CPC11.2 10/01/83 The error trapping within RBBS-PC was completely re-written to be more comprehensive. CPC12.0 10/28/83 Tree-structured file directories and the ability to detect that RBBS-PC was in a "MultiLink" environment were incorporated. "MultiLink" is a product of the Software Link, Inc. which allows DOS 1.1, 2.0, 2.1, and 3.0 to be "multi-tasking." CPC12.1 12/18/83 The ability for a SYSOP who signed on (Versions A-F) remotely to drop into DOS was added. Also the "New" command was added that allowed users to determine what new files had been made available since the last time they were on. Page 8 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 RBBS-PC Version Release Date of Major Enhancements Number First Version CPC12.2 04/08/84 The security system designed by Ken Goosens (Versions A-D) was incorporated. RBBS-PC's security system has an elegance unmatched even by the largest mainframe. In essence it is a "self-locking lock." Despite the fact that the RBBS-PC source code is distrbuted with RBBS-PC, the security system within RBBS-PC that Ken designed has remained unbroken. Of course, SYSOP's who didn't adhere to RBBS- PC's security structure have had their system "crashed" and every SYSOP should operate as if the very next caller could crash his system. CPC12.3 11/11/84 This was almost as total and as major a (Versions A-B) re-write of RBBS-PC as CPC10.0 had been. Beginning with CPC12.3 up to nine RBBS-PC's can share the same files in either a multi- tasking DOS environment (i.e. MultiLink from the Software Link, Inc.) or in a local area network environment (i.e. Corvus or Orchid). CPC12.4 03/10/85 RBBS-PC's stature in the industry became (Versions A, recognized when RBBS-PC was granted a A1, and B) license by Microcom to incorporate their proprietary MNP protocol into RBBS-PC. Almost at the same time many manufactures recognized the institution that RBBS-PC had become in our industry and elected to include "RBBS-PC compatibility" in their minimum criteria for the introduction of their new products. RBBS-PC's Vendor Support Program is more fully explained in the RBBS-PC documentation but one direct result of this was the intro-duction of 300/1200/2400 support in CPC12.4A before most such modems were generally available. CPC12-5 07/14/85 RBBS-PC was enhanced to allow 36 copies of (Versions A RBBS-PC to share the same files in a network and B) environment. RBBS-PC automatically answers the phone and no longer requires each caller to enter up to 3 carriage returns in order for RBBS-PC to detect the users baud rate and parity. Logon to RBBS-PC has been made much more efficient with the USERS file no longer being searched sequentially and the MESSAGES file no longer being read three times. Version CPC12-5B, released August 25, 1985, IS THE LAST VERSION COMPILABLE BY VERSION 1.0 OF THE IBM BASIC COMPILER! N O T E!! ============> Future versions will be compilable by both the Version 2.0 of the IBM BASIC compiler ($495 list price) and Microsoft's QuickBASIC Version 1.0 ($99 list price). However, only .EXE files generated from the QuickBASIC compiler will be tested and supported. Page 9 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 During the evolution of RBBS-PC I have had the distinct privilege of working with many contributors. Contributions have ranged from suggestions, to software fixes, to significant enhancements, to improved documentation. While I have met very few of these people personally, those whose names I remember are: Everett Delano Loren Jones Harvey Pierce Drew Commins Larry Jordan Danny Plunkett Mike Brown Robert Jueneman Dick Rohrdanz Don Dewall Verne Kallejian Rich Schinnell Jim Fox Steven Linhart Andrew Silber Warren Fox Scott Loftesness Carl Spencer Jim Fry Harry Logan Dorn Stickle Kent Galbraith Tom Mack Terry Steichen Ken Goosens Jon Martin Yew Seng Tan Read Gilgen Robert Mahoney Arnold Thomsen Dave Hacquebord Sidney Markowitz Clark Walker Steve Harrison Wes Meier Robert White Gary Hoff Bill Newkirk Gary Horwith Juergen Nordhausen Charlie Innusa To those whose names have not been mentioned -- apologies are extended. Take comfort in knowing that you live on in the work that you have wrought. Jon Martin is primarily responsible for whatever technical excellence that exists in RBBS-PC -- including the ability to have multiple RBBS-PC's share the same files. I am not a programmer and didn't even know BASIC until I started writing RBBS-PC and released RBBS-PC CPC10.0 in July of 1983. Jon's commitment to RBBS-PC has at least matched my own. Despite my own ineptness, Jon's patience, understanding, and technical insights have been unfailing over these many months and, I would like to both publicly acknowledge his contributions to RBBS-PC and express my appreciation for his efforts on behalf of RBBS-PC. I'd also like to mention Ken Goosens' efforts on behalf of RBBS-PC. Ken took the time and trouble to wade through the BASIC source code and incorporated the "security" system that exists within RBBS-PC today. Anyone who looks at the code can appreciate the magnitude of Ken's efforts. I wish space allowed me to chronicle the contributions of each of the contributors to RBBS-PC. In an age of cynicism, RBBS-PC and the Userware concept represents an opportunity for each of us to give back to the world something a little better than when we found it. As I said in section 1, this is something that I believe in strongly. To each of the contributors to RBBS-PC I would like to say personally "I am very proud of the company that RBBS-PC keeps." All changes to RBBS-PC since CPC10.0 have been "ADDITIVE." By that I mean CPC12.5B will run in the same environment and in the same way as CPC10.0. I felt that users should not be forced to choose between features (i.e. I can run either the features on CPC11.2 or the features on CPC12.1). 1.4 RBBS-PC Update Conventions ------------------------------- As RBBS-PC continues to evolve and be "debugged" the following coding conventions have been helpful in the past and you are requested to observe them in the future: Page 10 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 Updates consist of two ASCII files. One called xxxxxx.MRG which are the BASIC source statements to be merged into CPC12.3 as released by the Capital PC Software exchange. The second file is called xxxxxx.DOC which groups each line number in xxxxx.MRG into the specific functions added and describes the general feature added or bug that was fixed. Obviously xxxxxx can be anything you wish to name it. The second file will help the poor soul that must integrate several .MRG files and resolve whatever conflicts that may exist (i.e. yours truly). The RBBS-PC naming conventions of CPCxx.x are roughly as follows: 1. If a "bug" is being fixed CPCxx.x will be given a .MRG file name such as CPC12-1D.MRG with a corresponding CPC12-1D.DOC file describing the changes on a line number by line number basis. The first version of CPCxx.x is always "A". When you logon to RBBS-PC the version will be displayed. 2. If a new feature or enhancement is added the last digit in the CPCxx.x will be incremented by one (i.e. CPC12.2D was followed by CPC12.3A). 3. If a significant change to source code or logic occurs, the first two digits of the release level will change (i.e. CPC11.2 was followed by CPC12.0) The purpose of these conventions is to allow everyone to know what RBBS-PC level they are running under (users as well as SYSOP's) and understand the logic behind the changes/fixes as they occur so each SYSOP can evaluate them for his own needs. If you have comments or fixes please let us know so that they can be reflected in the RBBS-PC program and shared with all other users. You can do that by sending your changes by mail to: Capital PC Software Exchange PO Box 6128 Silver Spring MD 20906 or uploading the changes to the CPCUG's Software Exchange's BBS maintained by Rich Schinnell at (301) 949-8848. While comments and suggestions are always welcome, those that are accompanied by the RBBS-PC source code changes that implement them carry a lot more weight than those that don't. 1.5 An Example of "Users Helping Users" --------------------------------------- The ability to have multiple RBBS-PC's running concurrently -- either on a single PC in a multitasking DOS environment or in a local area network, is a concrete example of the concept of "users helping users" in action. This ability was developed in support of the efforts of the State of West Virginia Department of Education's "West Virginia Microcomputer Educational Network" project. It is the first statewide microcomputer network and encompasses all of the state's 1,125 schools in 55 different school districts. Each school is intended to have the capability of accommodating up to twenty IBM PC's in a local area network sharing a common 20MB disk drive. As of June of 1984, 83 of the 1,125 schools had such networks. Each PC can communicate with either the LAN, a central library, or with other schools in order to share programs and materials. The key component for this communication is RBBS-PC. In a presentation at the U.S. Department of Education in Washington, D.C.on June 22, 1984, the role RBBS-PC plays was described as follows: Page 11 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 "The medium that ties the entire system together -- that allows for communication not only between one school and another but also between schools and the central library -- is an electronic bulletin board (RBBS-PC) This bulletin board will be in operation 24 hours a day at the central site, with a similar bulletin board in operation at every school. The local school bulletin board (RBBS-PC) could be accessed by students who wish to review their lesson or take a test at home provided they had a computer and a modem. Teachers could access their grade book or other reports and lessons at home in preparation for the next school day. Neither bulletin board system (RBBS-PC) requires personnel to answer telephones or transmit files. They are both totally unmanned and operate 24 hours a day. No toll charges, of course, would be assessed for calling the local school bulletin board and toll free 800 numbers are used for accessing the central library." The State of West Virginia arranged to have the vendors involved, IBM and Corvus, make the appropriate equipment available on a "loan" basis so that RBBS-PC could be developed to work in a local area network environment. Since this project conformed so closely to the primary objectives of RBBS- PC, we agreed to volunteer our time and take on the task of enhancing RBBS- PC to allow up to nine (9) copies of RBBS-PC to execute concurrently sharing many of the same files. On a single PC the maximum number of concurrently running RBBS-PC's within the same DOS is limited only by: a. the number of communications ports installed on the PC. IBM's limit is two (COM1 and COM2), but other vendors supply "add-on" cards which provide for up to eight communications ports on a single PC. b. the number of communications ports that the IBM BASIC compiler can read and write to. IBM's limit is two (COM1 and COM2). c. the number of concurrently running tasks that can be supported. IBM's DOS is limited to one task. Other vendors provide "add-on" software to IBM's DOS that provides for up to nine simultaneous tasks. Within a network environment (i.e. multiple PC's linked together sharing the same devices) the maximum number of concurrent RBBS-PC's is set by RBBS-PC's internal design to nine (9). This design was based on the fact that anyone who wanted to run nine RBBS-PC's sharing the same set of files would take the $46,000 needed to buy nine PC's with modems, network interface cards, hard disk (at least 20MB) and purchase a microcomputer for the same amount of money with more ports and storage. For those interested in further information on the State of West Virginia's Microcomputer Educational Network, please contact: Mr. John E. Cook State of West Virginia Department of Education 1900 Washington Street East Building 6, Room 221, Capital Complex Charelston, West Virginia 25305 Page 12 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 1.6 What's New With CPC12.5B ----------------------------- CPC12.5B (and it's companion program CONFIG.BAS version 1.8) is essentially a maintenance release intended to correct all the known problems of CPC12.5A. With the availability of two new BASIC compilers, QuickBasic from Microsoft for $99 and Version 2.0 of the IBM BASIC compiler for $495, CPC12-5B will be the last release of RBBS-PC that will be compilable under the Version 1.0 of the IBM BASIC compiler. Since Microsoft's QuickBasic compiler is a subset of IBM's new Version 2.0 BASIC compiler, future versions of RBBS-PC will be compilable under both compilers. However, only RBBS-PC.EXE files generated by Microsoft's QuickBasic compiler will be tested. If the RBBS-PC.EXE file generated by the IBM Version 2.0 BASIC compiler fails to function correctly, it is suggested that you contact IBM and request the kind of support your $495 should entitle you to. Version CPC12-5B HAS NO NEW ENHANCEMENTS over CPC12-5A. It is absolutely a maintenance release. The primary errors that are corrected in 12-5B are: 1. RBBS-PC no longer requires the "ring indicator" signal (i.e. pin 22) unless the SYSOP wants to use "ring-back" or RBBS-PC to answer the phone only after the "nth" ring. Correcting the earlier dependency on the "ring indicator" will allow more modem's and systems to run RBBS-PC. 2. Users are now notified of the date and time that they where last on. Correcting this security laspe allows users to know if someone is accessing a system with their name and password. 3. The time in "chat" mode is no longer counted against a users elasped time. Correcting this error, hopefully, will encourage more exchanges of ideas. 4. Users can no longer enter mail to adressees that are not in the USERS file. Correcting this error insures that users can not send mail to "phantoms" except to those "phantoms" (i.e. AUTHORS) which the SYSOP has established. 5. Users are now told that either Ctrl K or Ctrl X can interrupt file transfers. 6. "WRK" has been added to those files that require binary transfers. 7. Uploads that are for the SYSOP only (i.e. whose descriptions begin with a "/") no longer have the description lost. It is now added to the CALLERS file. 8. Users who are locked out and call back are denied any future access if they commit another security violation. This corrects the problem of those who continually attempt to break RBBS-PC's security being allowed to call back indefinitely. 9. The problem with the SYSOP function # 2 not displaying all the users has been corrected. 10. The problem of RBBS-PC placing the last message read in the main MESSAGES file when coming back from a public conference has been corrected. Page 13 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 11. The problem of searching for a user with SYSOP function 5 causing RBBS-PC to go into a loop has been corrected. 12. When searching the drive's available for uploading (if more than one), all drives are now searched. 13. The error that allowed the SYSOP to exceed the maximum number of lines per message has been corrected. 14. The error where when selecting a nonexistant conference that would still place that conference name in front of the menu prompts has been corrected. 15. Users are only authorized to read messages no longer can reply to them or kill them. 16. CONFIG has been substantially re-written. The fundamental design change in CONFIG was to create USERS and MESSAGES files (or updates thereto) at the time that an option is selected rather than waiting until the SYSOP ends the CONFIG session. Additionally, when creating or maintaining "conferences" the SYSOP is graphically reminded that CONFIG is in conference maintenance mode. This design change virtually eliminates problems experienced with earlier versions of CONFIG when creating either public or private conferences. A new field was added to the "checkpoint" record (i.e. the first record of a message/conference file) that indicated the maximum number of messages allowed in the message/conference file. 2.0 RBBS-PC "BASE-LINE" HARDWARE REQUIREMENTS --------------------------------------------- RBBS-PC CPC12-5B is designed to run on an IBM Personal Computer running IBM's Disk Operating System (DOS), communicating via an IBM Asynchronous Communications Adapter and a Hayes Smartmodem 1200 modem. For RBBS-PC CPC12-5B the following equipment and software is recommended: IBM PC or IBM PC XT or IBM PC AT 80 column monitor Asynchronous communications adapter (serial port) Hayes Smartmodem 1200 (or 100% Hayes compatable!) Voice grade telephone connection for modem 25 pin RS-232-C modem cable (for stand alone modem) 192K RAM Two double sided drives Printer PC-DOS 2.0 or higher BASICA 2.0 or higher The compiled version of RBBS-PC, RBBS-PC.EXE, is approximately 107K and (if MNP protocol is included) is approximately 138K. DOS 2.0 and DOS 2.1 both take slightly more than 24K. In order to run RBBS-PC.EXE within a 128K configuration you would have to compile and link RBBS-PC without the MNP protocol support and the only DOS available to you is DOS 1.1. Of course, with only 128K you would have no room for a RAM drive. A minimum of 192K is recommended unless you are running under DOS 1.1 or the BASIC interpreter. Under the BASIC interpreter, the multiple RBBS-PC and MNP capabilities are unavailable! Also you may choose to run RBBS-PC on only a single double sided drive or two single sided drives. However the less disk space available the more Page 14 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 file maintenance the SYSOP must do. If you have a second telephone installed specifically for RBBS-PC, ask for a second voice grade telephone line. Data lines are very expensive and are not necessary. The program requires the use of a Hayes 1200 Smartmodem (or one that is 100% Hayes compatable) in order to function properly. If your non-Hayes modem doesn't work with RBBS-PC, send RBBS-PC (source code and all) to the vendor and ask him to expalin why it doesn't work (i.e. why it is "incompatable" with the Hayes 1200). Callers who come in at even parity and 7 data bits, then try to change to no parity and 8 data bits to use XMODEM may have a problem if they are using PC-TALK and a Hayes Smartmodem. Switch 1 on the caller's modem has to be down (the factory default position) or the carrier will be dropped when the communication parameters are switched. To avoid this the PC- TALK caller will have to enter the escape code (factory setting "+++"), reset the modem parameters with Alt-P and/or Alt-F, and then return to the "connect" state with the command "ATO." Callers who wish to communicate at 450 baud have to call in at 300 baud then switch to 450 using the N)ew baud selection from the "Utilities" menu. Beginning with version CPC12-5B, RBBS-PC does not require PIN 22 to be hooked up on the RS-232-C cable (that's the cable which runs between the modem and the computer) except when a non-zero value is selected for option 9 of CONFIG. In order for RBBS-PC to answer the phone on a specified ring number, the modem must send a "ring-indicator" signal to to RBBS-PC. This is the way that RBBS-PC detects that the phone is ringing when a SYSOP has selected option 9 of CONFIG to either answer on a specified number of rings or on a "ringback". PIN 22 is the ring indicator coming from the modem going to the computer. Just because you bought an RS232 cable, don't assume that it has PIN 22 connected. The $55 12-pin RS232 cable sold by many computer stores often does not have PIN 22 connected. For about $18 in parts from Radio Shack you can put together your own RS232 cable with all the pins connected. Recently a friend of mine paid $14.88 (including postage) for a RS232 cable with all the pins connected by ordering part number CDB25P-4-S from Jameco Electronics (their telephone number is 415 592-8097). 3.0 RBBS-PC's Support Policies ------------------------------ 3.1 RBBS-PC's Vendor Support Policy ----------------------------------- The only reason RBBS-PC is "hardware-specific" to the IBM PC and the Hayes Smartmodem is that these have pretty much set an industry standard (let's not debate the issue of whether they have also set a "technology" standard). If you follow the code in RBBS-PC closely, you will notice that a great deal of effort was expended in order not to be "hardware-dependent" on either the Hayes or the IBM PC. The purposes of RBBS-PC are outlined in section 1.0 of the RBBS-PC documentation. Those who contribute to RBBS-PC do so without any hope of monetary reward. In fact great lengths are taken to assure that neither those involved with the development of RBBS-PC nor anyone who distributes RBBS-PC does so for either personal gain or to promote a specific product at the expense of other products. If the hardware you are using is not part of the "base-line" hardware and RBBS-PC doesn't work, your only recourse is to either modify RBBS-PC to meet your particular hardware's needs (that's why the source code is distributed) or contact your vendor and ask him to fix his hardware or modify RBBS-PC (via a .MRG file) to support his hardware. Page 15 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 During 1984 RBBS-PC became something of an "industry standard." As such several manufacturers have requested that support for their particular hardware and/or software be incorporated into RBBS-PC. These vendors have had three choices: 1. Obtain a copy of the BASIC source code by sending $8 to the Capital PC User Group's Software Exchange. The source code allows the vendor to determine what is required to be "RBBS-PC compatible" and who better knows the quirks of the manufacturer's product, than the manufacturer? RBBS-PC's limited license specifically permits the distribution of ".MRG" files that would allow RBBS-PC to run with whatever idiomatic quirks a specific vendor's product exhibited. The advantage to the manufacturer is that he is in complete control; he need not make the .MRG "universal" (i.e. it need only support his product). The disadvantage is that new releases of RBBS-PC come out every six to eight weeks and the vendor would have to review each release and make sure the new releases and his .MRG files were compatible. Of course, as for any other RBBS-PC operator, casual telephone support is available to these vendors. 2. Supply the necessary equipment or software on a loan or gift basis to be used in the testing of future releases of RBBS-PC. This approach has been actively DISCOURAGED for three fundamental reasons. First the vendor perceives he has "paid" for on-going support by the loan or donation of the product. This is not the case because RBBS-PC's development is an all-volunteer activity. As such neither I nor any of the others involved with the development of RBBS-PC may have the time nor expertise sufficient to assure compatibility of the specific vendor's product with future releases of RBBS-PC. About all that can be done is to give the vendor our "best effort" to assure compatibility, and advise him when it can not be made compatible. Second, the particular product may not have a universal applicability to RBBS-PC users and (or) may not be of interest to those who regularly contribute to the development of RBBS-PC. Both of these conditions must exist before any vendor's product is incorporated into the RBBS-PC development cycle. Third the price of the loaned or donated products (usually 3 to 5 such products) in no way can even begin to compensate for the hundreds (if not thousands) of development hours required to support other than "base line" hardware. 3. Establish an on-going institutional commitment to maintain a dialogue between the vendor's engineering group and the RBBS-PC development team along with supplying the necessary equipment or software on a loan or gift basis to be used in the testing of future releases of RBBS-PC. This approach has been actively ENCOURAGED for three different and fundamental reasons. First the vendor overtly makes an institutional commitment to jointly participate in the development of RBBS-PC. The vendor has the opportunity to supplement the all-volunteer activity that is the basis for RBBS-PC development by choosing to either modify his current or future products to be compatible with RBBS-PC or to Page 16 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 supply software that ensures compatibility with RBBS-PC. This benefits all RBBS-PC users. Second, the particular products that fall into this category are required to have a universal applicability to RBBS-PC users (i.e. multi-tasking DOS, networking, 2400 baud capability, error-free protocols, etc.). Also a regular contributor to RBBS-PC 's development must be geographically located close to the vendor's development engineers to assure a timely dialogue. Further any regular contributor to RBBS-PC's development who accepts the responsibility for assuring RBBS-PC's compatibility with a particular vendor's product must be willing to do so solely on a volunteer basis over an extended period of time and in such a way as not to exclude other vendor's products. Only when all of these conditions exist is any vendor's product a candidate to be incorporated into the RBBS-PC development cycle. This assures that the RBBS-PC user community has a feed-back mechanism to the vendor's product development and design teams and the vendor is assured of a matching long-term commitment from the RBBS-PC development team. Third the vendor recognizes that the price of the loaned or donated products (usually 3 to 5 such products) is minuscule compared with the hundreds (if not thousands) of man-hours that may be required from both the RBBS-PC development team as well as the vendor's engineers. This assures that the vendors who choose this later approach are committed to the PC user community and it is precisely this type of commitment that RBBS-PC's USERWARE concept is designed to encourage (from both users and vendors) Vendors who have chosen to make this third type of commitment to RBBS-PC and the PC user community deserve the respect and encouragement of every PC user and are (alphabetically): Ark Electronic Products, Inc. 325 W. Hibiscus Blvd. Melbourne, Florida 32901 (305) 724-5260 Corvus Systems, Inc. 2100 Corvus Drive San Jose, California 95124 (408) 559-7000 Hayes Microcomputer Products, Inc. 5923 Peachtree Industrial Blvd. Narcross, Georgia 30092 (404) 449-8791 International Business Machines Corporation (Internal Zip Code 2900) P.O. Box 1328 Boca Raton, Florida 33432 (305) 998-2000 Microcom, Inc. 1400A Providence Highway Norwood, MA 02062 (617) 762-9310 Page 17 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 Multi-Tech Systems, Inc. 82 Second Avenue, S.E. New Brighton, Minnesota 55112 (612) 631-3550 Orchid Technology 4790 Westinghouse Drive Fremont, CA 94539 (415) 490-8586 Prometheus Products Incorporated 4545 Cushing Parkway Fremont, CA 94538 (415) 490-2370 Racal-Vadic 1525 McCarthy Blvd. Milpitas, California 95035 (408) 774-0810 The Software Link, Inc. 8601 Dunwoody Place Suite 336 Atlanta, GA 30338 (404) 998-0700 Users who feel that they have benefited or who appreciate such commitment to the user community should write or call the above vendors and tell them so, especially if such a commitment influenced the purchase of their products. Similarly, if any user feels another vendor should make a similar commitment to RBBS-PC and the user community, write that vendor and send a copy of your letter to the following address: Tom Mack 10210 Oxfordshire Road Great Falls, Virginia 22066 APPENDIX B describes the RBBS-PC specifications for those vendor's of proprietary protocols who would like to have them added to future releases of RBBS-PC. 3.2 RBBS-PC User Support Policy ------------------------------- RBBS-PC is an all-volunteer effort on my part. Professionally I am not a programmer (as anyone who has looked at the source code can testify) nor an "expert/guru" on personal computers. Since I am not independently wealthy, I have a full time job (unrelated to PC's). As with most other folks, I'm also busy raising a family. What time I can spare from these other activities I am glad to donate to answer questions about RBBS-PC as I believe (somewhat fanatically) in the Userware concept. However, if you have questions regarding something other than the "base- line" hardware and software requirements outlined in section 2.0, DON'T CALL ME. I probably can't help you anyway and even if I do venture some advice it will probably be wrong. One of the axioms of the "userware" concept is that every user should be able to help themselves -- that's why there are 77 pages of documentation and the source code is distributed. The only calls that I truly appreciate are those that reveal BOTH a problem and a solution. These I am more than happy to share with anyone and are as rapidly as possible included in RBBS-PC (either the documentation, the Page 18 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 software, or both). Of course, if you encounter a problem and 1. read and re-read the documentation, 2. spend days and days attempting to isolate it, 3. called other SYSOP's and asked their help, 4. run RBBS-PC under the BASIC interperter to isolate the problem area in the code, 5. looked up any error messages you encountered (they are in the BASIC manual that comes with your IBM PC's DOS), 6. know what version of RBBS-PC that you are running, 7. know what version of CONFIG that you are running, 8. eliminated all other software from your environment, and still can not get RBBS-PC to work, I am most happy to lend whatever telephone advice I can. In this world it helps to remember that there are only two types of problems -- MY problems (which are the ones that I can solve) and OTHER PEOPLE's problems (which are the ones that I can't solve). 4.0 OPERATING SYSTEM REQUIREMENTS --------------------------------- Under the basic interpreter RBBS-PC uses the FILES function to determine the amount of free space available on the disks for comments, messages, uploads, and the SYSOP. Under DOS1.1's BASICA this FILES function does not return the amount of free space or file sizes and, hence, this information is unavailable. Under the compiler available free space is returned by the use of an assembler subroutine (UTILITY). 5.0 HOW TO GET A COPY OF RBBS-PC SENT TO YOU -------------------------------------------- RBBS-PC can be obtained by sending a check for $8 to the Capital PC Software Exchange P.O. Box 6128 Silver Spring MD 20906. RBBS-PC is distributed on two double-sided, 9-sector, diskettes. Allow 3 to 4 weeks for delivery -- remember this is an all-volunteer effort. The exigencies of RBBS-PC software releases may mean that diskette 18 contains an earlier version of RBBS-PC than CPC12-5B (either you bought diskette 18 awhile ago or there has been not enough time for diskette 18 to be updated to this most current version). Not to fear! Your $8 has not been wasted. At least three bulletin boards keep the most current copies of RBBS-PC CPC12-5B for downloading. They are: (703) 759-5049 --+ +---- East Coast (Great Falls, Virginia), (703) 759-9659 --+ (202) 537-7475 ------- East Coast (Washington, D.C.), and (415) 689-2090 ------- West Coast (Concord, California). Page 19 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 6.0 FILES RBBS-PC USES ---------------------- There are essentially two types of files that RBBS-PC uses -- "system" and "text" files. "System" files are defined as random files that RBBS-PC reads and writes to. "Text" files are defined as files that RBBS-PC primarily reads from which can be edited externally to RBBS-PC with most text editors that can handle ASCII files. Either type of file can be "static" or "variable" in length. By "static" it is meant that these files have a pre-defined length beyond which RBBS-PC does not extend them. Similarly, "variable" length files are defined as those files whose length is dynamically increased by RBBS-PC. In a multiple RBBS-PC environment only the "static" length files can be shared SAFELY among the various RBBS- PC's. The following table summarizes, using the default file names, which category the different RBBS-PC files fall in: "Static" Length Files "Variable" Length Files ----- /|\ MESSAGES CALLERS System USERS COMMENTS Files MESSAGES.BAK 99.DIR (upload directory) \|/ USERS.BAK upload disk ----- RBBSxPC.DEF ----- BULLET /|\ BULLET1 --> BULLETn | DIR.DIR | aa.DIR --> bb.DIR Text FILESEC and PASSWRDS Files HELP01 --> HELP08 | MENU1 --> MENU5 | NEWUSER \|/ TRASHCAN & CONFENCE ----- WELCOME In a CORVUS network environment some of the "static" length files can be shared on a common volume and ALL of the "variable" length files must be segregated on volumes unique to each copy of RBBS-PC. RBBS-PC issues the NAME function of BASIC in order to determine if a file exists. Because of this all the volumes accessed by any RBBS-PC in a CORVUS network must be designated "read/write." Therefore, you must be very careful when running CONFIG.BAS which creates the definition file (RBBSxPC.DEF) for each copy of RBBS-PC that you layout the RBBS-PC files as follows: Page 20 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 Sharable RBBS-PC Files in a Non-sharable RBBS-PC Files in a CORVUS network (i.e. on a CORVUS network (i.e. each RBBS-PC common volume) has a volume dedicated to it.) ----- CALLERS /|\ MESSAGES COMMENTS System USERS 99.DIR (upload directory) Files MESSAGES.BAK upload disk \|/ USERS.BAK RBBSxPC.DEF ----- BULLET /|\ BULLET1 --> BULLETn | DIR.DIR | aa.DIR --> bb.DIR Text FILESEC and PASSWRDS Files HELP01 --> HELP08 | MENU1 --> MENU5 | NEWUSER \|/ TRASHCAN & CONFENCE ----- WELCOME In a MultiLink (i.e. from the Software Link, Inc.) environment and in Orchid's PC-NET environment the vendor's claim that not only all the "static" length files can be shared on a common volume but also some of the "variable" length files can be shared. However, if you want to be as conservative as possible, run RBBS-PC in ALL environments as if it where running in a CORVUS network environment. However, if you rely on the vendor's claims, in either a MultiLink or PC-NET environment, when running CONFIG.BAS which creates the definition file (RBBSxPC.DEF) for each copy of RBBS-PC you must be careful to layout the RBBS-PC files as follows: Sharable RBBS-PC Files in a Non-sharable RBBS-PC Files in a MultiLink or PC-NET enviro- MultiLink or PC-NET environment nment (i.e. shared on a (i.e. each RBBS-PC has a volume common volume) dedicated to it with these files on it). ----- /|\ MESSAGES, MESSAGES.BAK CALLERS | USERS, USERS.BAK System COMMENTS Files 99.DIR (upload directory) | upload disk \|/ RBBS-PC.DEF ----- ----- BULLET /|\ BULLET1 --> BULLETn | DIR.DIR | aa.DIR --> bb.DIR Text FILESEC and PASSWRDS Files HELP01 --> HELP08 | MENU1 --> MENU5 | NEWUSER \|/ TRASHCAN & CONFENCE ----- WELCOME 6.1 RBBS-PC System Files ------------------------- As shown above, "system" files are both static and variable in length. The system files used by RBBS-PC are: Page 21 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 MESSAGES - This file is a random file that contains the message text for the RBBS-PC system. The first record in the file contains the RBBS-PC "checkpoint" record. The records immediately following this first record are the RBBS-PC "node" records. The rest of the file consists of message header records which are followed by the message text for that header. Appendix A describes the fields and their uses within the various type of records of the messages file. RBBS-PC expects the messages file to exist and to have been created by CONFIG.BAS. If CONFIG.BAS does not find the MESSAGES file or it finds one in pre-CPC12-3A format, it will create it and initialize it to the size the SYSOP specifies. Because of the fixed length records in this file, it should not be created or edited outside RBBS-PC. When the SYSOP "packs" the message file using CONFIG.BAS, the file MESSAGES.BAK is created to hold the old messages in case the "pack" is unsuccessful (i.e. not enough space to duplicate the message file). If the disk fills up during the pack function RBBS-PC will recover the message file using MESSAGES.BAK. When the messages file is successfully packed, the pre-packed messages file is renamed MESSAGES.OLD and the temporary file MESSAGES.BAK is renamed MESSAGES. The MESSAGES file should only be "packed" in a multiple RBBS-PC environment when there are no RBBS-PC's active. The MESSAGES file can be shared among multiple RBBS-PC's. USERS - The users file is a random access file that has a record for each user that used the system. The record contains a profile for each user that has logged on to RBBS-PC. Appendix A describes the format of the records within the USERS file. The records are 128 bytes in length and are automatically maintained by RBBS-PC. The SYSOP can do some limited editing using SYSOP function 5. To initialize the system simply ERASE this file. RBBS-PC expects the USERS file to exist. If CONFIG.BAS does not find the file on the system it will create it to the size specified by the SYSOP. The USERS file should not be created or edited outside CONFIG.BAS. When the SYSOP "packs" the user file using CONFIG.BAS, the file USERS.BAK is created to hold the old users in case the "pack" is unsuccessful (i.e. not enough space to duplicate the users file). If the disk fills up during the pack function RBBS-PC will recover the USER file with USERS.BAK. When the users file is successfully packed, the pre- packed users file is renamed users.OLD and the temporary file USERS.BAK is renamed USERS. The USERS file should only be "packed" in a multiple RBBS-PC environment when there are no RBBS-PC's active. The USERS file can be shared among multiple RBBS-PC's. CALLERS - This file is a random file that contains a log of all callers as they sign-on the system along with callers city and state, the date and the time. The names are added to the end of the file as well as are the names of the files uploaded/downloaded by the caller. If the file is not found RBBS-PC will create a new one. The file should be ERASED to clear the log. The CALLERS file can not be shared among multiple RBBS-PC's. COMMENTS - This file is a sequential file that contains any comments that have been left by users for the SYSOP. The file can be scanned by a SYSOP function or it can be TYPEd or edited outside the RBBS system. A SYSOP function is available to delete this file, or it can be emptied outside of DOS. The file will be created by RBBS-PC if it is not found. The COMMENTS file can not be shared among multiple RBBS-PC's using CORVUS' "OMNINET". This file can be shared using Multi-link or Orchid. 99.DIR - The file on the upload disk that is to have the name, file size, date, and description appended to it of files that have been uploaded. The 99.DIR file can not be shared among multiple RBBS-PC's using CORVUS' "OMNINET", but can be shared using Multi-link or Orchid. Page 22 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 RBBS-PC.DEF - This is an ASCII text file created as output by the CONFIG.BAS file. It contains the configuration parameters for the RBBS. It is read by RBBS to determine the configuration settings tailored to your RBBS- PC. In a multiple RBBS-PC environment the definition file for each RBBS-PC is named RBBSxPC.DEF where "x" is a number 1 through 9 , 0 (for the tenth copy), and A through Z (for the eleventh through 36th copy) corresponding to which copy RBBS-PC it describes. In a multiple RBBS-PC environment, (i.e. using "OMNINET") each RBBS-PC should have a unique volume that the other RBBS-PC's should not write to (they may read from) on which to write it's CALLERS, COMMENTS, 99.DIR, RBBSxPC.DEF, and file uploads. In a "OMNINET" network with four RBBS-PC's, the disk volumes would all have to allocated as both read and write. The SYSOP would have to carefully set up each RBBSxPC.DEF file using CONFIG.BAS such that the actual access was as follows: Physical Physical Physical Physical Physical Volume "D" Volume "E" Volume "F" Volume "G" Volume "H" RBBS-PC #1 READ/WRITE Read-only Read-only Read-only Read-write RBBS-PC #2 Read-only READ/WRITE Read-only Read-only Read-write RBBS-PC #3 Read-only Read-only READ/WRITE Read-only Read-write RBBS-PC #4 Read-only Read-only Read-only READ/WRITE Read-write Physical volume "H" would contain all the sharable RBBS-PC files. The files that are "sharable" are a function of the type of environment that the multiple RBBS-PC's are running in (see section 6.0). Each copy of RBBS-PC would have it's own physical volume that all the other copies of RBBS-PC would access as "read-only" and which it could access as "READ/WRITE." This "READ/WRITE" volume would contain all the non-sharable RBBS-PC files. The files that are "non-sharable" are a function of the type of multiple RBBS-PC environment that RBBS-PC is running in (see section 6.0). RBBS-PC displays the status of those files which must be locked in a network environment on line 25. The lock status of the message file is displayed in positions 68 & 69. The lock status of the user file is displayed in positions 71 & 72. The lock block status is displayed in positions 74 & 75 and comments/uploads share positions 77 & 78. The letter "U" in the first position shows that the file is currently "UNLOCKED". The letter "L" in the first position indicates that the file is "LOCKED". 6.2 RBBS-PC Text Files ----------------------- Similarly, the RBBS-PC "text" files are both static and variable in length. The "text" files used by RBBS-PC are: BULLET - This is a text menu file that is printed following the WELCOME file when a user first enters the system. It must be present, if "CONFIG Utility parameter # 43" is greater than 1. It can also be called from the main menu with the <B>ulletins command. BULLET1 --> n -- There can be 1 to 99 "bulletins". RBBS-PC will check for the existence of a file whose name consists of the prefix given by parameter 44 of CONFIG.BAS appended with the bulletin number and using parameter 41 of CONFIG.BAS to determine the drive to find the bulletin on. Users can elect to have displayed two different types of "graphics" files for such standard RBBS-PC system files as HELPxx, BULLET, MENU's, etc. In Page 23 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 order for a user to see either of these two different types of "graphics" files, the following must have occured: logged on N/8/1, requested graphics (either full ASCII or "color/music"), and the file must exist and the filename end in either: "G" for files containing the graphic ASCII characters whose values are in the range 129 to 256, or "C" for files containing combinations of the full 256 characters that the caller's communication software can interpert and translate into colors and music (i.e. PC-TALK.666, QMODEM, and EXECPCT). RBBS-PC will check to see if a "graphics" files exists by appending a "G" or "C" to the file name. If such a file can't be found, RBBS-PC will check to see if a non-graphics file exists (i.e. one without the "G"). RBBS-PC will display the first file it finds or a message that the file can not be found. DIR.DIR, aa.DIR --> nn.DIR -- At least one DIR.DIR file has to be present on one of the drives available for downloading. Alternative directories, aa.DIR --> nn.DIR (see section 10), should be meaningful and should be reflected in the DIR file. FILESEC - is more fully described in the section on security. HELP01 --> HELP09 -- Represent the nine on-line help files for RBBS-PC users. They are associated with the following areas: HELP01 -text file that is printed when <H>elp is requested on the main function prompt. It contains command information. HELP02 -text file that is printed when a <?> is entered on the main function prompt. It is also printed following the NEWUSER file for new users and tells users what functions the RBBS supports. HELP03 -text file that describes the message protection options when <?> is entered after the message <E>nter command is executed at the main message menu. HELP04 -text file that describes the message entry subfunctions when <?> is entered at the subfunction prompt. HELP05 -text file that is printed when <H>elp is entered in the files subsystem function prompt. HELP06 -text file that is printed when a <?> is entered in the files subsystem function prompt. HELP07 -text file printed when <H>elp is requested at the message read prompt. HELP08 -text file printed when <H>elp is requested in the utility subsystem function prompt. HELP09 -text file printed when <H>elp is requested for type of graphics a user wants (none, ASCII, color/music). MENU1->5 -- contain the various commands for the subsystems. It is recommended that these be placed on an electronic disk drive (i.e. RAM) Page 24 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 rather than on a floppy or hard drive. NEWUSER - This is a text file that is displayed for new users just before registration occurs. PASSWRDS - is more fully described in the section on security. TRASHCAN - is a text file that contains names that the SYSOP finds objectionable and does not want used as either a users first or last name. RBBS-PC uses this file, if it exists, to deny access to anyone using one of these names for either their first or last name. WELCOME - This is a text file that is printed when a user first enters the system. It must be present, and it should be modified to identify your system. CONFENCE - This is a text file that is printed when a user selects the J)oin function from the main menu. It should be created using your favorite text editor and should contain a list of the conferences that you have on your system. 7.0 USING THE "CONFIG" UTILITY TO CONFIGURE RBBS-PC CPC12 --------------------------------------------------------- The RBBS-PC.DEF file you get (which, if you don't have it originally, is created for you by the CONFIG.BAS program) contains the program's default operating parameters and values. When you run the CONFIG.BAS program to either create RBBS-PC.DEF or to update it, you can change many of these parameters to meet your needs. Certain parameters which control critical operations of the programs are embedded in the RBBS program and should not be normally be changed by the system operator. Unless a value or parameter is noted here, it should be changed only with great forethought and caution. CONFIG.BAS, unlike Gaul, is divided into eight parts or screens. They are: Screen Description 1 Global RBBS-PC Parameters (Part 1 of 2) 2 Global RBBS-PC Parameters (Part 2 of 2) 3 Parameters for RBBS-PC "text" files 4 Parameters for RBBS-PC "system" files 5 Parameters for RBBS-PC "doors" 6 Parameters for RBBS-PC Security 7 Parameters for Multiple RBBS-PC's and "conferences" 8 RBBS-PC Utilities The user may scroll forward or backward through the 8 screens of parameters in CONFIG.BAS using the PgUp and PgDn keys on the keyboard. Additionally users may go directly to a specific screen by pressing a function key (F1 through F8) coressponding to the page to be selected. To terminate CONFIG, users need only press the "End" key on the keyboard. The compiled version of CONFIG.BAS can be invoked with the command: CONFIG.EXE This assumes that the compiled version of CONFIG.BAS, CONFIG.EXE is on the default disk drive. CONFIG.BAS will write the RBBS-PC definition file, RBBSxPC.DEF to the default drive. Page 25 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 7.1 Global RBBS-PC Parameters (Part 1 of 2) ------------------------------------------- 7.1.1 SYSOP's Name and Password for Remote Access. -------------------------------------------------- Parameters 1-4 request the RBBS system operator's (SYSOP) name and dual passwords. When logging onto the system remotely, the SYSOP can log on using Password #1 for his first name and Password #2 for his last name, in which case the system will recognize him as SYSOP and allow him to perform all the SYSOP functions even as a remote user. The SYSOP name is used to insure that users are not attempting to access RBBS-PC using the SYSOP name hoping to get a higher access level. Attempting to logon using the SYSOP name will result in "LOGON DENIED" and a posting of the attempt in the CALLERS file. If you want to eliminate anyone from logging on as the SYSOP, you can simply reply with a "null" (i.e. a carriage return) to Password #1 and Password #2. 7.1.2 Password to Locally Take Over RBBS-PC as SYSOP ---------------------------------------------------- The ESC key is used to log on in local SYSOP mode. Parameter 5 allows a password to be required if someone hits Esc on the keyboard of the PC running RBBS-PC before they are considered a local SYSOP. If you enter NONE, no password is required. 7.1.3 SYSOP's default sign-on mode ----------------------------------- Parameter 6 sets the system operator's sign-on mode as EXPERT or NOVICE. Unless you a very familiar with the RBBS-PC CPC12's command structure, the SYSOP's sign-on mode should be NOVICE. 7.1.4 SYSOP's "office" hours ---------------------------- Parameter 7 is the SYSOP's "office hours" (i.e. when he can be paged by a user). The IBM PC's bell is rather insistent, and these hours should be set to match when you will be within ear-shot of the RBBS- PC. The times are set using a 24-hour military clock (i.e. 10:00 P.M. is 2200 hours). NOTE: These hours can be overridden by activating the page bell (F4). 7.1.5 Use of Printer Bell ------------------------- Parameter 8 allows allows the SYSOP to elect to have the bell on the printer sounded (it is usually louder than the PC's) when he is being "paged". 7.1.6 Number of Rings RBBS-PC Waits Before Answering ---------------------------------------------------- Parameter 9 specifies the number of rings to answer the phone on. Specifying 0 means that RBBS-PC will answer the phone as soon as it rings. Specifying a number greater than 2 means that RBBS-PC will either: 1. wait until the number of rings specified to answer the phone, or 2. answer the next call after the current one after the number of rings specified providing the next call comes within 45 seconds after the first call stops ringing the phone (i.e RINGBACK). Specifying a number greater than one is only useful when a single phone line can receive a mixture of both voice (i.e. callers who wish to Page 26 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 speak with the SYSOP) and data calls (i.e. for RBBS-PC) on an unscheduled basis. In this type of environment (i.e. a random mix of voice and RBBS-PC calls), there are two ways a SYSOP can set up RBBS-PC so that RBBS-PC can automatically determine if the call is for the SYSOP or for RBBS-PC. First, the SYSOP can establish the rule that if he is unable to come to the phone, then RBBS-PC will answer it if the phone rings the number of times specified in option 9. Callers can let the phone ring and (if it is not answered by a person within some agreed on number rings) know that it will be answered by RBBS-PC. This is useful to those who may have either a hearing or speech problem and are unable to use the telephone conviently for voice communications by themselves. A second approach is the more classic, "ring-back" approach. RBBS-PC can be told to NEVER answer the first call (it can ring forever!). However should the caller WAIT A MINIMUM OF 12 SECONDS (a Hayes restriction) and call back no later than 45 seconds after the last ring of the first call, RBBS-PC will answer the call after the number of rings indicated in parameter 9 providing the number of rings are set to between one and five. If someone wants to make a voice contact, they simply call and let the phone ring until it is answered. If you have a dedicated line for your RBBS-PC (either full time or on a scheduled basis), parameter 9 should be set to ZERO. 7.1.7 Drive Available for Uploading ----------------------------------- Parameter 10 specifies the letter of the single drive available that this copy of RBBS-PC can upload files to. When a file is uploaded, the file specified by CONFIG parameter 11 will be automatically appended with the file name, file size, date of upload, and short description as specified by the user. 7.1.8 Name of Directory to Update for Uploads --------------------------------------------- Parameter # 11 of the CONFIG program asks for the name of the directory into which the file name, file size, and file description of uploaded files can be recorded. The default name is 99.DIR and it must be a text file on the drive designated for uploading (see section 7.1.7). 7.1.9 Drives Available for Downloading -------------------------------------- Parameter 12 specifies the letters of the drives from which files can be downloaded. The order in which they are specified is the order in which the drives will be searched. If the order is BAC, then drive B will be searched first for the file, then drive A, and finally drive C. While there can be duplicate files on each of the drives, the first file found, will be the one downloaded to the user. 7.1.10 Prompt Sounds (can be changed by SYSOP from keyboard, too) ----------------------------------------------------------------- Parameter # 13 is the SYSOP'S preference for prompt sounds when input is required. This applies to remote and local. 7.1.11 Maximum Time on Per Session ---------------------------------- Parameter # 14 of the CONFIG program asks for the maximum amount of time each user is to be allowed on the system per session. Set the Page 27 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 number of minutes to whatever you are comfortable with, but 72 minutes is a good setting for starting up. Subsequently you may have to lower this number once your number of callers increases, in order to keep callers' waiting times reasonable. This can also be made the maximum time on the system per day. As described in section 13.3, each security level can have it's own maximum time on the system per session specified 7.1.12 Limit Maximum Time on System Per Day ------------------------------------------- You may limit the maximum amount of time any single user can spend on your system each day via parameter 15 of CONFIG. This is helpful if you have a relatively busy RBBS and want to have as diversified group of callers as possible. What this parameter does is to tell RBBS-PC to keep track of the total amount of elapsed time a user is on RBBS each day. Each time he logs on the maximum amount of time that he is allowed on the system is checked against this daily cumulative total. The time remaining in each of his session is the difference. When he exceeds this maximum and tries to logon again, he is told that he has exceeded his allocated time for that day and to try again tomorrow. 7.1.13 Months of Inactivity Before a User is Deleted ---------------------------------------------------- Parameter # 16 sets the number of months inactivity that must elapse before a user is deleted from the USERS file when the SYSOP "packs" the user file (see section 7.8.2). 7.1.14 Communication Port to be Used ------------------------------------ Parameter # 17 requests the user to specify the communication port that RBBS-PC will be using in order to determine if it is device COM1 or device COM2 (the later is valid only for DOS 2.0 and above). 7.1.15 Version of DOS RBBS-PC Will Run Under -------------------------------------------- Parameter 18 allows the SYSOP to specify the version of DOS that RBBS-PC will be running under. When RBBS-PC is running this is the ONLY indicator used by RBBS-PC when it has to determine what level of DOS it is running under. The correctness of this parameter will is very significant when RBBS-PC options are invoked using commands specific to DOS 2.0 and above (i.e. the CTTY command for SYSOP function 7). 7.1.16 Name of RBBS-PC ---------------------- Parameter # 19 allows the SYSOP to specify the name of the RBBS-PC that is to be displayed when a user first connects with the system and prior to completing the logon process. 7.2 Global RBBS-PC Parameters (Part 2 of 2) ------------------------------------------- 7.2.1 Color Monitor's Foreground/Background/Border -------------------------------------------------- Parameters 21 through 23 allow the SYSOP to specify the colors he wishes for the foreground, background, and border. When specifying these options the BASIC manual's section describing the COLOR command in text mode should be consulted. This is useful when running multiple RBBS-PC's and you want a handy way of determine which RBBS-PC it is that you are viewing on the screen. This option is Page 28 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 specifically used to indicate the status of whether "RING-BACK" is activated (i.e. the RBBS-PC.DEF file with "ring-back" enabled would have a different border than the color border defined in the RBBS- PC.DEF file for a dedicated line.) 7.2.2 Selecting the Modem Speaker On or Off ------------------------------------------- There are times when the SYSOP no longer wants the speaker to be activated when a user logs on. The noise can drive anyone nutty on a busy RBBS-PC bulletin board (especially late at night). Option 24 allows the SYSOP to keep the modem speaker turned off at all times. 7.2.3 Reminding Users of Messages They Left ------------------------------------------- Option 25 allows the SYSOP to remind users not only of the messages that might be for them but also messages that they may have left. This should be enough of a nuisance to insure that users do delete some of the message that they have left and help to keep the MESSAGES file to a minimum. 7.2.4 Remind Users of Uploads and Downloads ------------------------------------------- Parameter 26 allows the SYSOP to elect to remind users of how many files that they have downloaded and uploaded. 7.2.5 Remind Users of Their Profile Preferences ----------------------------------------------- Parameter 27 allows a SYSOP to always remind users when they first logon of the preferences they have selected for such things as file transfer protocol, graphics, nulls, etc. 7.2.6 Default User Page Length ------------------------------ Parameter 28 allows the SYSOP to establish a default page length for users when they logon. A 23 line page length is the default, but the SYSOP can set it to a number between 0 and 255. If set to 0, the user will receive continuous output. 7.2.7 Maximum Number of Lines Per Message ----------------------------------------- Parameter 29 allows the SYSOP to specify (within the range of 1 to 30) the maximum number of lines allowed in each message. 7.2.8 Requiring non-ASCII Protocol for Binary Files --------------------------------------------------- Option 30 allows the SYSOP to tell RBBS-PC that files ending in binary file extensions (i.e. .ARC, .EXE, .COM, .OBJ, .WKS, .BAS, or whose second letter of the extension is Q) can not be downloaded unless the user selects XMODEM or MNP. This will hopefully eliminate some user problems before they occur. IBM's BASIC interpreter's SAVE command default is to write files in a special binary format (also referred to as 'tokenized') because they require much less disk space. 7.2.9 MICROCOM's MNP Protocol ----------------------------- Option 31 allows MNP to be optional within RBBS-PC. Some SYSOP's may not wish to provide their users with the choice of MNP protocol (especially if they are employed by a company that has a competing protocol). RBBS-PC's features and growth are designed to be "additive." This parameter allows each SYSOP to decide if MNP protocol Page 29 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 is to be available for file transfers. Microcom's error-free protocol, MNP, is available for file transfer beginning with version CPC12-4A of RBBS-PC. The RBBS-PC.EXE file includes code from the MNP library. The MNP library file provided with RBBS-PC is done so under the following condition: "The MNP library file provided with RBBS-PC is the exclusive proprietary property of Microcom, Inc. and this copyrighted program material is supplied by Microcom exclusively for use with the RBBS-PC bulletin board system. Inclusion of library code within RBBS-PC does not in any way grant a license to the Microcom Networking Protocol (MNP). The use of the RBBS-PC MNP library code modules or MNP in any product other than the RBBS-PC program is a violation of Microcom's proprietary rights in the MNP technology." See section 18.0 of the documentation for the special considerations for linking RBBS-PC with the MNP library. 7.2.10 Omitting First Level Directory in "New" Command ----------------------------------------------------- Option 32 allows the SYSOP to exclude the primary directory (DIR.DIR) from the search done by the New command. If you have multiple directories (i.e. RBBS.DIR through BASIC.DIR), any dates in the primary directory would not be of files. The "New" command (as in "What new files have been put on the download directories since I was last on?") search each line of each file whose extension is DIR for a date field. Since the first level directory is normally a listing of the other directories and their general subject areas, it is advisable to omit the first level directory from the "New" command. 7.2.11 Omitting Upload Directory in "New" Command ------------------------------------------------ Option 33 allows the SYSOP to exclude the directory on which users place the information on their uploads (i.e. 99.DIR) from the "New" command. As some SYSOP's wish to preview or otherwise keep private the uploads before putting them on the download directories, this acts as a further insurance against unauthorized access of a "private" upload directory. 7.2.12 Making System Welcome Interruptable ------------------------------------------ Option 34 allows the SYSOP to make the system "welcome" file interruptable. The default is that YES it is interruptable. However, if the SYSOP feels too many people are bypassing it and it contains essential information, the SYSOP can set this parameter to NO (i.e. the user can not suspend or cancel the listing of this file at his terminal with a CTRL S or CTRL K). 7.2.13 Making System Bulletins "Optional" ----------------------------------------- Parameter 35 is intended to allow the SYSOP to indicate if the system bulletins are to be an option for users when they log on. 7.2.14 Is RBBS-PC running on a non-IBM PC? ------------------------------------------ Option 36 is designed to allow RBBS-PC to run on some "IBM-compatible" PC's that make use of unused interrupts. RBBS-PC checks to see if the unused interrupt X'7F' is non-zero. If it is, RBBS-PC thinks that the software product, MultiLink (from The Software Link, Inc.) is present Page 30 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 and issues the appropriate MultiLink calls. Obviously if this is not the case, strange and unpredictable things happen resulting in RBBS-PC not working. The COMPAQ+ is just such an example of this syndrome. 7.2.15 Issuing Modem Commands Between Rings ------------------------------------------- Option 37 allows the SYSOP to tell RBBS-PC either to wait to issue commands in between rings or to issue modem commands without waiting. Some modems can not both handle the telephone ringing and accept modem commands simultaneously. Other modems, like the Hayes, can handle such simultaneous demands. For these later (i.e. Hayes, Prometheous, Multi- Tech, etc.) this option should be set to "NO." 7.2.16 Baud Rate to Initially Open Modem At ------------------------------------------- Some 2400 baud modems (like the Hayes) MUST be initially opened at 2400 baud because they can only "bump down" when automatically detecting baud rate when answering the phone (i.e. from 2400 down to 1200 down to 300). Parameter 38 allows the SYSOP to select the baud rate at which RBBS-PC is to initially open the modem at. 7.2.17 Seconds Waited Before Logging Off Idle Users --------------------------------------------------- The SYSOP can select the number of seconds that RBBS-PC will allow a user to be "idle" (i.e. not entering or receiving data) via parameter 39. 7.3 Parameters for RBBS-PC "text" Files --------------------------------------- 7.3.1 Drive Containing RBBS-PC "Bulletins" ------------------------------------------ Parameter 41 indicates the disk drive on which RBBS-PC is to search for bulletins when a user requests to see them. 7.3.2 Name of File Describing the "Bulletins" --------------------------------------------- This is the text file that is shown to a user if bulletins are not optional (see parameter 35) or if the user replies "L" when notified of how many bulletins exist (see parameter 43). This file should contain a list of the bulletins (i.e. 1-99) and a brief one-line description of the contents of each (i.e. "New Release of RBBS-PC"). 7.3.3 Number of System Bulletins -------------------------------- Parameter 43 allows a SYSOP to have from 0 to 99 "bulletins." If there are 0 bulletins a user is notified that there are no bulletins. Bulletins should be brief, informative, and timely. I personally think that there should be very few bulletins and that they should be changed often if users are to be enticed to look at them. 7.3.4 Prefix Used to Name Bulletin Files ---------------------------------------- Parameter 44 provides the SYSOP with the flexibility to make the prefix of the bulletins anything he wants (i.e. BULLET). To this is added the number (i.e. BULLET7 for bulletin number 7) and the disk drive designated in parameter 41 is searched for the bulletin number requested when some asks to see a bulletin. If the file is not found, the user is so informed. If a "graphics" equivalent is found and the user has signed on N/8/1 and requested graphics, the graphics version of the bulletin is displayed (i.e. BULLET7G). Page 31 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 7.3.5 Drive Containing On-Line Help Files ----------------------------------------- Parameter 45 indicates the disk drive on which RBBS-PC is to search for to find RBBS-PC's on-line "help" files whenever a user asks for help within a specific subsystem. 7.3.6 Prefix Used to Name "Help" Files -------------------------------------- There are nine on-line "help" files used by RBBS-PC as described in section 6.2 previously. The SYSOP may chose to have them named something other than HELP01 through HELP08. Parameter 46 allows the SYSOP to pick up to a seven character prefix to which the numbers 1 through 9 will be appended. This file name is what RBBS-PC will look for on the drive specified in parameter 45 when a user asks for help on-line. As with "bulletins", if a "graphics" equivalent is found and the user has signed on N/8/1 and requested graphics, the graphics version of the help file is displayed (i.e. HELP7G). 7.3.7 Name of "NEWUSER" file ---------------------------- This is the text file that each new user sees when they first logs on and before they "register" themselves in RBBS-PC's USERS file. A user sees it once and only once during his first session. It can contain anything that you want it to, but a brief explanation of your Board's purpose, "rules", etc. might be appropriate. Parameter 47 allows the SYSOP to give the file any name he wants. 7.3.8 Name of "WELCOME" file ---------------------------- This is the text file that each user sees EVERY time they log on. Keep it brief! RBBS-PC will look for a "graphics" equivalent if the user qualifies for graphic displays (i.e. it will display the file HELLOG in lieu of HELLO). Parameter 48 allows the SYSOP to tailor this file's name to his own tastes. 7.3.9 Name of File Describing File Directories ---------------------------------------------- See Section 10.0 for a description of file directories -- they have no relation to DOS 2.x and above "sub-directories!" Since the BASIC compiler Version 1.0 supplied by IBM doesn't recognize DOS 2.x and above "sub-directories", RBBS-PC can't. This is an IBM limitation not an RBBS-PC one! Most SYSOP's categorize the files that are available for downloading into general groups (games, utilities, etc.). Parameter 49 allows the SYSOP to name the file that describes these groupings anything he wants. 7.3.10 Name of SYSOP's Command Menu ----------------------------------- Parameter 50 allows the name of the text file containing the commands allowed those with SYSOP privileges to be any name he wants it to be. Since such files are constantly accessed, it is recommended that the "menus" be placed in a RAM disk in order to cut down on the wear and tear of your disk drives. 7.3.11 Name of Messages Subsystem Command Menu ---------------------------------------------- Parameter 51 allows the name of the text file containing the commands available to those in the "messages" subsystem to be any name he wants it to be. Since such files are constantly accessed, it is recommended that the "menus" be placed in a RAM disk in order to cut down on the Page 32 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 wear and tear of your disk drives. 7.3.12 Name of File Subsystem Command Menu ------------------------------------------ Parameter 52 allows the name of the text file containing the commands available to those in the "files" subsystem to be any name he wants it to be. Since such files are constantly accessed, it is recommended that the "menus" be placed in a RAM disk in order to cut down on the wear and tear of your disk drives. 7.3.13 Name of Utilities Subsystem Command Menu ----------------------------------------------- Parameter 53 allows the name of the text file containing the commands available to those in the "utilities" subsystem to be any name he wants it to be. Since such files are constantly accessed, it is recommended that the "menus" be placed in a RAM disk in order to cut down on the wear and tear of your disk drives. 7.3.14 Menu that Lists Available Conferences -------------------------------------------- Parameter 54 is the name of the text file listing the names of the conferences that are available. Conference names must be seven characters or less. Additionally, the SYSOP must have already pre- formatted the messages and users files associated with the conferences (see section 16.0). 7.3.15 File Containing Invalid User Names ----------------------------------------- Parameter 55 is the name of the text file listing names that the SYSOP considers inappropriate. This file is used when a new user signs on. The new users first and last name is checked, individually against the names in this file. The format of this file is as follows: <name>, An example of such a file would be: KILLER, MAN, THE, DOC, DOCTOR, DEATH All names should be UPPER CASE! If you create the file using IBM's standard DOS text editor, EDLIN, each line should end with a comma. If you create the file using COPY CON, each line should end with a carriage return (i.e. the "enter" key). The last line (when using COPY CON) should end with F6 then carriage return. BASIC will treat either a comma or a carriage return as a field deliminator and you need a field deliminator following each of the names. If the above file existed, any new user who logged and used the following names would be denied access: Byte Killer Kilo Man Doctor Death PC Doctor The Best Page 33 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 7.3.16 Factor to Extend Session Time For Uploads ------------------------------------------------ Parameter 56 allows a SYSOP to "reward" users who upload files by adding some multiple of the elasped time it took for the file upload to the current session time. This should be used judiciously as some users may abuse this by repeatedly uploading COMMAND.COM or some other meaningless file. This only extends the user's current session and NOT the elasped time he may be limited to per day via parameter 15. 7.3.17 Default System Type for New Callers ------------------------------------------ Parameter 57 allows a SYSOP to set the default system type for new users to something other than IBM PC (i.e. KAPRO, COLUMBIA, WANG, etc.). 7.4 Parameters for RBBS-PC "system" Files ----------------------------------------- 7.4.1 Name of "MESSAGES" file ----------------------------- Parameter 61 allows the SYSOP to specify the file name for the file used by RBBS-PC to hold the messages on the bulletin board. This file can NOT have a qualifier because RBBS-PC appends the qualifier ".BAK" to the file name when "packing" the messages file. 7.4.2 Name of the "CALLERS" file -------------------------------- RBBS-PC maintains a log of user activity on a "callers" file. It contains information on the date, time, mode, of who logged on; what they uploaded or downloaded; and any security violations or errors that were generated. Parameter 62 allows the SYSOP to specify the fully qualified name for the file that RBBS-PC uses for this log. 7.4.3 Name of file containing "Comments" for the SYSOP ------------------------------------------------------ Instead of leaving a "message", a user may leave a comment for the SYSOP that is readable only by the SYSOP. Parameter 63 allows the SYSOP to specify the fully qualified name for the file used by RBBS-PC to store users' comments. 7.4.4 Name of the "USERS" file ------------------------------ RBBS-PC keeps a profile of each user that logs on in a "user record" (see Appendix A for a layout of this record). Parameter 64 allows the SYSOP to specify the file name for this file. This file can NOT have a qualifier because RBBS-PC appends the qualifier ".BAK" to the file name when "packing" the users file. 7.5 Parameters for RBBS-PC "Doors" ---------------------------------- 7.5.1 Enabling the "Door" Subsystem ------------------------------------ Parameter 81 allows the SYSOP to enable RBBS-PC to exit to whatever "doors" the SYSOP has set up into his system. A "door" is simply a batch file that the SYSOP has created which he is willing to allow his users to have RBBS-PC exit to and which will then take control of the remote users communication port. 7.5.2 Name of Menu that Lists the Available "Doors" --------------------------------------------------- Parameter 82 allows the SYSOP to specify the fully qualified file name Page 34 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 of the menu that lists the names of the "doors" available to his users. RBBS-PC checks this file to verify that the name of the door that the user requested is in the door's menu. (See Section 12) 7.5.3 File RBBS Builds Dynamically to Open a "Door" --------------------------------------------------- Parameter 83 allows the SYSOP to specify the fully qualified file name of the file that RBBS-PC is to use when building a file to exit to and invoke a "door." This is also the same file name that is used when the SYSOP exits to DOS. 7.5.4 File to Re-invoke RBBS-PC when a "Door" Closes ---------------------------------------------------- When a door finishes RBBS-PC is re-invoked. Parameter 84 allows the SYSOP to specify the fully qualified file name of the .BAT file that should be used to re-invoke RBBS-PC (see section 11 & 12). This is also the same file name that is used when the SYSOP returns from exiting to DOS. 7.6 Parameters for RBBS-PC's Security ------------------------------------- 7.6.1 Minimum Security Level to Get Into RBBS --------------------------------------------- Parameter 101 specifies the minimum security level a users needs to logon onto RBBS. If the default is less than this value no new users can logon on (i.e. the board is closed to pre-registered users). Since RBBS-PC is intended to facilitate the free exchange of information, you are strongly urged not to use RBBS-PC in this way. 7.6.2 Default Security Level for New Callers -------------------------------------------- Parameter 102 specifies the security level that will be assigned to all new callers. At the very least it is recommended that this value be equal to the security level assigned to the C>omments and G>oodbye commands via option 109. 7.6.3 Default Security Level for SYSOP -------------------------------------- Parameter 103 allows you to specify the minimum security level a user must have to be considered an "assistant" SYSOP by RBBS-PC. Even if a user has a high enough security level to see the SYSOP's menu and execute some or all of the SYSOP commands, the user will not be treated as a SYSOP (i.e. allowed to see the files upload/download when viewing the CALLERS file) unless his security level is equal to or greater than that specified by parameter 103. 7.6.4 File of File Names with Download Security ----------------------------------------------- Parameter 104 specifies the name of the file that contains a list of file names that CAN NOT BE DOWNLOADED (even if they are on the disks that are available for downloading) unless the user supplies a password and/or is at a specific security level. If you want to have no file security at all, just put no file names in this file. If you include a password with a file name all users (including one with SYSOP privileges) must be able to give the password in order to download the file. For a more detailed description of this file and how it works, see section 13.4 -- "How to Implement the Security for Download Files." Page 35 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 7.6.5 Minimum Security Level to See SYSOP's Menu ------------------------------------------------ Parameter 105 prevents the SYSOP menu from being displayed (even if the user has a security level of a SYSOP as specified in option 103) unless the user is also at this security level. 7.6.6 Minimum Security Level to Use RBBS-PC "Doors" --------------------------------------------------- Parameter 106 allows the SYSOP to set the minimum security level a user must have to exit RBBS-PC via a "door". This security level must be equal to or higher than the security level for the "D>oor" command (see Parameter 110). 7.6.7 Maximum # of Security Violations Before Lockout ----------------------------------------------------- Parameter 107 allows a maximum number of security violations (i.e. attempts to download protected files) before the user is logged off and locked out. 7.6.8 Security Levels for Each Command -------------------------------------- Parameters 108 through 111, allow the SYSOP to set up the security levels required to issue the commands in the SYSOP, Main Menu, File Subsystem, and Utilities Subsystem (respectively). All the commands in each area can be given the same security level or, optionally, a specific command can be given a unique security level. 7.6.9 File with Privileged Group Passwords ------------------------------------------ Parameter 112 specifies the file name which contains the privileged group passwords that allow users to temporarily change their security, time on the system, etc. -- if the SYSOP has set it up that way. Callers shift to a group password by changing passwords. If the password they select is found in the file containing the privileged passwords, their private logon password is unchanged and they receive the security level and/or time limit associated with the group password. If you have no group passwords, just put nothing in this file. For a more detailed description of this file and how it works, see section 13.3 -- "How to Implement the Password File." 7.6.10 Maximum # of Password Changes Per Session ------------------------------------------------ Parameter 113 allows the SYSOP to specify the maximum number of times a user can change his passwords in a given session. 7.6.11 Minimum Security for Temporary Password Changes ------------------------------------------------------ Parameter 114 is the minimum security level required in order for a user to temporarily change his security or time on the system via privileged group passwords. 7.6.12 Minimum Security to Overwrite Files on Uploads ----------------------------------------------------- Parameter 115 allows the SYSOP to specify a security level that has the privilege of overwriting files (i.e. files that already exist) when uploading. 7.6.13 Security Level of Conference "Viewers" --------------------------------------------- Parameter 116 allows the SYSOP to specify a temporary security level Page 36 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 that will be in effect when a user wishes to "view" a conference. In this way a user might be able to S>can (i.e. see the date, time, subject, etc.) of the messages in a conference without having to be pre-registered in the conference. Not currently implemented (as of CPC12-5B). 7.6.14 Security Level Exempt from Purge of USERS File ----------------------------------------------------- When the SYSOP "purges" the USERS file, all users who have not signed on within the number of months specified in parameter 16 are deleted from the file with the exception of those who have been "locked out" and those whose security level is equal to or greater than that specified in parameter 117. 7.7 Parameters for Multiple RBBS-PC's ------------------------------------- 7.7.1 Maximum Number of Concurrent RBBS-PC's -------------------------------------------- RBBS-PC CPC12-5B allows multiple RBBS-PC's to run in the same environment/network and share many of the same files. If you ever plan to do this or if you are going to do this, set this number to the MAXIMUM number you ever envision running. Up to 36 RBBS-PC's can share the same files. Depending on the environment, 4 to 5 copies of RBBS- PC's may turn out to be the operationally effective maximum. Parameter 121 allows you to specify the maximum number of RBBS-PC's that the MESSAGES file should be initialized for. 7.7.2 Environment Running Concurrent RBBS-PC's ---------------------------------------------- Parameter 122 allows the SYSOP to designate the type of environment that multiple copies of RBBS-PC will be sharing files in. This is necessary so that RBBS can use the mechanism that is appropriate to the specific environment when sharing files. RBBS-PC CPC12-5B currently can handle the following environments for multiple RBBS-PC's: 1. MultiLink (The Software Link, Inc.) 2. OmniNet (Corvus) 3. PC-Net (Orchid) 7.7.3 Method RBBS-PC Uses to "Recycle" When Users Logoff -------------------------------------------------------- Some local area network environments are not designed to have applications constantly branch back to the beginning and re-open already open files. If you are in this environment or simply want to run some external program after a users logs off or RBBS-PC recycles, parameter 123 allows you to elect to do this. If you specify "internal", RBBS-PC will function as it currently does and branch back to its beginning. If you specify "system", RBBS-PC will exit to DOS and (if you are running RBBS-PC out of a .BAT file) you can then automatically invoke any other "housekeeping" programs you want before re-invoking RBBS-PC. It should be noted that this will add a considerably delay to RBBS-PC's re-cycling time as RBBS-PC will have to reloaded back into memory every time it re-cycles. 7.7.4 Maximum Number of Records in the "USERS" File --------------------------------------------------- Like the MESSAGES file, the USERS file must also be static in length for RBBS-PC CPC12-5B. Parameter 124 allows the SYSOP to set the size of the USERS file. RBBS-PC automatically keeps track of the records Page 37 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 available for use in this file and does the necessary "housekeeping." When the USERS file get full (i.e. all its records are used up) and the SYSOP neither "packs" it nor increases the size of the file, no new users will be able to logon until one of these two events occurs. 7.7.5 Maximum Number of Records in the "MESSAGES" File ------------------------------------------------------ RBBS-PC CPC12-5B requires that the "Messages" file be static in length. It automatically keeps track of the next record available and does the necessary housekeeping to maintain the integrity of the file. Parameter 125 allows the SYSOP to set the size of this file. CONFIG.BAS will automatically determine what size the current file is and will reformat a pre-CPC12-3A MESSAGES file if it finds one. If you do not increase the size of your existing MESSAGES file, no one will be able to leave any new messages. Similarly, when the MESSAGES file get full (i.e. all its records are used up) and the SYSOP neither "packs" it nor increases the size of the file, no one will be able to leave a message until one of these two events occurs. The minimum size of the MESSAGES file is equal to 1 (The "checkpoint" record) + the maximum number of concurrent RBBS-PC's ("node" records) + the maximum number of messages allowed X 5 (each messages is assumed to use an average of five 128-byte records). Therefore, if option 121 of CONFIG where 12 and option 126 of CONFIG where 50, the minimum number of records that could be specified for option 125 is 263 ( 1 + 12 + ( 50 *5 ) ). 7.7.6 Maximum Number of Messages Allowed ----------------------------------------- Parameter # 126 lets you set the maximum number of messages on the system that you will allow. The number will have to be based on the size of the average message on your bulletin board. Most messages require about 600 bytes on the average. The absolute upper limit on the number of messages is 250. If you specify 250 messages, you can expect that the MESSAGES file will be preformatted to more than 160K in size. 7.7.7 Conference File Maintenance --------------------------------- Parameter # 127 allows "conference" files to be maintained. A "conference" consists of a message file and, if a "private" conference, a corresponding users file. The name of the conference can be anything that the SYSOP selects but can not be longer than 7 characters. The message file's name for a conference consists of the conference name plus the characters "M.DEF". The user file's name assocated with "private" conferences consists of the conference name plus the characters "U.DEF". Parameter # 127 allows the SYSOP to create, expand, or contract either or both of the files associated with a "conference." This occurs ONLY when the SYSOP "ENDs" the CONFIG session by pressing the key marked END. Parameter # 127 allows the SYSOP to perform all the functions on page 8 of CONFIG on the conference that he has named/selected with Parameter # 127. For a further discussion of "conferences" see section 16.0. 7.8 RBBS-PC SYSOP Utilities --------------------------- 7.8.1 Packing the "MESSAGES" file --------------------------------- The message file contains all messages for the RBBS-PC system. As messages are killed they are only flagged as inactive. Parameter 141 Page 38 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 should be used periodically to recover the space occupied by the killed messages. After completion, only the text of active messages will be present and the old file will remain on the system with the name of MESSAGES.OLD. Also, you will need enough free disk space for the MESSAGES and MESSAGES.BAK files when packing the MESSAGES file or the packing cannot be performed; if enough space is not found the packing will abnormally terminate and the MESSAGES file will be recovered. 7.8.2 Rebuilding the "USERS" File --------------------------------- Parameter 142 removes deleted users and users who have not been on the system within the number of months specified using parameter 16 in CONFIG. You should have enough free disk space for USERS and USERS.BAK or the rebuilding will abnormally terminate (the USERS file will be restored). It is important to note that beginning with CPC12- 5A, the USERS file is no longer a random file that is accessed sequentially but now is a random file that is accessed directly. When a user logs on RBBS-PC "hashes" the users name to find his user record directly in the USERS file. That is why the USERS file's size is a power of 2 (i.e. 256, 1024, etc.). This allows users to logon much more quickly to RBBS-PC's that have a very large number of users. 7.8.3 Printing Message Header Records ------------------------------------- Parameter 143 will display the message headers of all messages, active and killed, that are present in the message file. This is left over from one of the many "debugging" stages of RBBS-PC prior to CPC09. Following the policy of making all changes "additive", this function has been retained. It may help some SYSOP's recover from disk hardware failures. 7.8.4 Renumbering Messages -------------------------- Parameter 144 permits messages to be renumbered sequentially starting from a specified message using whatever starting number you wish. Please note that there is not much error checking to be sure that the new numbers do not duplicate those of lower numbered active messages. When complete, the next message to be created will be the next higher number from the resequence. Unpredictable results will occur if a SYSOP creates messages with duplicate numbers! 7.8.5 Repairing the MESSAGES file --------------------------------- Parameter 145 goes through the MESSAGES file and reconstructs the chains that link the messages together. MESSAGES files that have "blank" messages or abbreviated messages (i.e. some lines of text are missing) can be repaired with this facility. 7.8.6 Initialize Hayes 2400 Firmware for RBBS-PC ------------------------------------------------ Parameter 146 allows the SYSOP to set the Hayes 2400 firmware to match RBBS-PC's requirements as described in section 8. Additionally, the SYSOP may elect to allow or not to allow remote users to use the Hayes 2400 that RBBS-PC is utilizing for remote digital loop back testing. Page 39 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 8.0 THE HAYES MODEM SWITCH SETTING AND CONSIDERATIONS ----------------------------------------------------- RBBS-PC is tested with a HAYES Smartmodem 1200 (i.e. external). The switch settings on the modem must be as follows: switch -- 12345678 setting - UUDDDUUD Recognizing that there are a number of "Hayes-compatible" (and not so compatible) modems in use, this section is intended to assist those adventurous souls who chose to use such modems and need some guidance on what the otherwise mystical Hayes switch settings mean. The following table may be of some help: Hayes Setting Function to RBBS-PC Switch Factory RBBS-PC 1 Down Up Allows RBBS-PC to control the modem using the RS-232C DTR lead (pin 20). 2 Up Up Not meaningful to RBBS-PC (could be down) and is used to indicate if result codes are to be English words or single digits. RBBS-PC sets this with the Hayes "V" command. 3 Down Down Not meaningful to RBBS-PC (could be down) and is used to indicate if result codes are to be sent to RBBS-PC. RBBS-PC sets this with the Hayes "Q" command. 4 Up Down The modem does not echo characters unless half-duplex is selected and the modem is on- line. 5 Down Down Modem is NOT to answer incoming calls. RBBS- PC monitors the ring indicator (pin 22) to determine if the phone is ringing. If it is RBBS-PC will issue the necessary commands to the modem. 6 Down Up RBBS-PC checks for the carrier signal using the RS-232C Carrier Detect lead (pin 8). If carrier is lost, RBBS-PC hangs up the phone and re-cycles to await the next call. 7 Up Up Not really required by RBBS-PC. However in the "down" position, the telephone extension light will illuminate on a multi-line installation when the modem answers a call. 8 Down Down Enables the Smartmodem 1200 to recognize the Hayes commands issued by RBBS-PC. These switch settings do not have to be changed for most other communications software packages. (You can leave the switches set as shown above if you use PC-TALK for your smart terminal communications. However, you will be advised to give the modem an "ATZ" command before using PC-TALK in order to reset the registers correctly.) RBBS-PC should only be used with versions 123 and above of the Hayes Smartmodem 1200 and version 247 and above of the Hayes Smartmodem 2400. Earlier versions do not answer Page 40 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 the telephone properly. The ATI command will cause the Smartmodem to tell you its version. The Hayes 300 modem doesn't function with RBBS-PC for reasons that Hayes has yet to figure out. Hayes is now shipping an external modem called the Hayes 1200FE that has 10 switch settings. To run RBBS-PC switches 9 and 10 of the 1200FE must be left up (the factory setting). Hayes is also now shipping an internal modem called the Hayes 1200BFE that has 6 switch settings. To run RBBS-PC switches 4, 5, and 6 must be left up (the factory setting). 9.0 COMMUNICATION BUFFER ------------------------ RBBS-PC should be operated with a 4096 byte communications buffer when running under the BASIC interperter. RBBS-PC can run under the BASIC interperter at 300 baud with a smaller buffer, but 450 and 1200 baud operation requires 4096 for uploads of large ASCII files. This is primarily because of the way the BASIC interperter performs "house cleaning" of it's string areas. The BASIC command to execute RBBS is as follows: BASICA RBBS-PC /C:4096 When running the compiled version of RBBS-PC (i.e. RBBS-PC.EXE), it is not necessary to have as large a communications buffer because the code generated by the IBM BASIC compiler is much more efficient when perfroming it's "house cleaning." When compiling RBBS-PC CPC12, the compiler command is as follows: BASCOM RBBS-PC.BAS /E/C:4096/S/O; Operation with a smaller buffer may result in communication buffer overflows and loss of data when using ASCII protocol for file transfers. Non-ascii protocols like XMODEM and MNP require only a 4,096 byte buffer because of the handshake file transfer technique employed. When setting up the communications buffer, be sure you leave enough free memory for string manipulation. BASICA (i.e. the BASIC interperter) needs at least 2048 bytes free to operate properly with this program. Anything less may cause the program to run out of string space, especially when a message is being written. When specifying the size of the communications buffer, remember that the amount of memory that will be reserved will be the number specified times the total number of communication ports. Therefore if you have a system with two communications ports and specify 4096, 4096 bytes will be allocated for EACH communications port even though each RBBS-PC only uses one communications port. Thus, the total reduction in string space will be 8K and not the 4K you might have expected. 10.0 USING MULTIPLE FILE DIRECTORIES ------------------------------------- With the advent of CPC12.0, multiple file directories for downloads were possible. A file directory IS NOT A DOS "SUBDIRECTORY!" It is simply a text file that the SYSOP has created which has a one-line entry for each file available for downloading in the format: file name extension xxxx mm-dd-yy description that associates a size, date and description for each file name/extension. There are a few conventions regarding download directories. They are as Page 41 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 follows: o The file directories must be text files. o The file directories must have an extension of up to three characters. The default extension is ".DIR". The 8-character suffix can be anything you want as long as it is a valid DOS file name. o There is only one file directory for uploads and it must be on the disk drive designated for uploads. o Filename should start in column 1. o Extension should start in column 10. o Program size can be between columns 14 & 22. o Date available for downloading must start in column 24 and should use MM-DD-YY or MM/DD/YY format. o Description should start in column 34. Most SYSOP's tend to organize their file directories according to subject. The primary file directory usually tells how you list the other directories. Logically, it looks like a tree structure as follows: DIR.DIR | | -------------------------------------------------------------- | | | | | | | | | aa.DIR bb.DIR ............................................ zz.DIR The suffixes aa through zz can be anything you want. Most RBBS-PC SYSOP's use numbers (i.e. 1.DIR, 2.DIR, etc.). The command L;2 would list 2.DIR. The SYSOP has the option of letting his users know the name of the file directory for uploads. Some SYSOPS do and some don't. You may exclude both the directory of directories and the upload directory from the list new function (N) within the file subsystem (see sections 7.2.10 and 7.2.11). 11.0 SETTING UP ".BAT" FILES FOR RBBS-PC ----------------------------------------- Many SYSOPS have set up batch files to automatically invoke RBBS-PC and to re-invoke RBBS-PC should there be a power outage. These files range from the simple to the sublime in terms of complexity. In a multiple RBBS-PC environment, these .BAT files CAN NOT BE SHARED, if you are either going to drop into DOS remotely (either via the SYSOP's option 7 or via "doors.") Both the SYSOP option 7 which allows a SYSOP who is signed on remotely to drop into DOS and the "doors" feature of RBBS-PC require that: 1. RBBS-PC be executed from a batch file. 2. That the batch file which is executing RBBS-PC contain an "IF" statement that checks for the existence of the batch file which RBBS-PC dynamically builds when either "doors" or the SYSOP function 7 is invoked. 3. Within the "IF" statement, the logic exists such that the batch file dynamically built by RBBS-PC for the "doors" functions or the SYSOP function 7 will be invoked if it exists. As a very simple example, let us assume 1. that the batch file that invokes RBBS-PC is named A:RBBS.BAT, and that is what was entered for option 84 of CONFIG.BAS, 2. that the name of the batch file that RBBS-PC will build dynamically for either "doors" or SYSOP function 7 is Page 42 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 A:RCTTY.BAT and that is what was entered for option 83 and 3. the compiled version of RBBS-PC is being executed and is named RBBS-PC.EXE and is on the default disk drive. 4. you have elected to use the watchdog utility program. Then A:RBBS.BAT (in a non-MultiLink environment) would contain the following: WATCHDG1 OFF IF EXIST A:RCTTY.BAT DEL A:RCTTY.BAT RBBS-PC X (see note of values available for "X") IF EXIST A:RCTTY.BAT WATCHDG1 ON IF EXIST A:RCTTY.BAT A:RCTTY.BAT A:RBBS.BAT If RBBS-PC is being run under the BASIC interpreter, RBBS-PC will use the RBBS-PC.DEF file for its configuration parameters and ignore what was on the parameter line that invoked RBBS-PC. This is the standard default for SYSOPs running a single copy of RBBS-PC. If you are running multiple copies of RBBS-PC, it is not possible to run RBBS-PC under the BASIC interpreter! If running RBBS-PC.EXE, RBBS-PC will check for the "X" in the command line that invoked RBBS-PC. The "X" on the execute line is extremely important to the correct operation of RBBS-PC. If you are running in a local area network environment then the "X" should be a number between "1" and "9". If "X" is omitted from the command line, RBBS-PC will look for a file named RBBS-PC.DEF. RBBS-PC uses the parameter in the command line to determine the correct RBBSxPC.DEF file to use for its configuration parameters. Obviously the RBBS.BAT file could be as complex as you wanted it to be, but at the very least it would need the "IF" statements. Page 43 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 12.0 THE USE OF RBBS-PC "DOORS" ------------------------------- The RBBS-PC "door" concept is that of allowing a SYSOP to set up a "door" through which his RBBS-PC users can exit from RBBS-PC and enter another application. In previous versions of RBBS-PC (i.e. prior to CPC12-3A) this had been called "windows" but because of the confusion this created with MicroSoft's WINDOWing concept, it has been re-labeled "doors". RBBS-PC's "doors" are nothing more than .BAT files that the SYSOP has created to allow his users to exit from RBBS-PC and enter other applications (i.e. data bases, etc.). The SYSOP is responsible for writing the .BAT files that he will allow users to invoke. Assuming that RBBS-PC is brought up by DOS via an autoexec file that invokes RBBS.BAT, a door called EDIT exists that consists of a .BAT file (EDIT.BAT) which contains the commands CTTY, EDLIN, and RBBS.BAT. Here is pictorially what happens: DOS | \|/ AUTOEXEC.BAT | \|/ RBBS.BAT | +--------->RBBS-PC.EXE | | RCTTY.BAT<-----invokes door called "EDIT" | \|/ EDIT.BAT | +--------->EDLIN.COM | | RBBS.BAT<--------ends | | +--------->RBBS-PC.EXE | | welcome back from door and RBBS-PC continues To set up "doors" the SYSOP lists the names of these .BAT files (which he is responsible for setting up) in MENU5. If the SYSOP has indicated that doors are available (via CONFIG.BAS' option 81), when a user invokes the D>oor command: 1. RBBS-PC will list MENU5, 2. Check that the door that the user selects was specified in MENU5, 3. Check that the .BAT file exists (on the default drive), 4. Dynamically create a .BAT file with the name specified by the SYSOP in option 83 of CONFIG.BAS that: a. invokes the .BAT file of the window specified,and b. re-invokes rbbs-pc after the user EXITS from the window by invoking the .BAT file that the SYSOP specified in option 84 of CONFIG.BAS. Page 44 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 The purpose of "doors" is to allow for the "horizontal" growth of RBBS- PC. Clearly RBBS-PC has about all that IBM's BASIC compiler can handle. In order to not limit the application of RBBS-PC either to BASIC or the current compiler, "doors" was chosen as a mechanism to allow SYSOP's to make available other features (i.e. data bases, games, etc.). Hopefully with RBBS-PC as a base, the limitation on doors are that of the SYSOP's resourcefulness AND IBM'S DISK OPERATING SYSTEM (see section 15)! The design of the .BAT file that is to be used as a "door" is critical and is the responsibility of the SYSOP. At the very minimum it should handle the communication port I/O. This can be done in a very primitive way using the DOS CTTY command and the "watchdog" utility written by described in section 20. Finally, if the preceding discussion of "doors" is a complete mystery to you, contact a SYSOP of an RBBS-PC that is using "doors" and ask him for help. The "door" concept stretches IBM's DOS' capabilities and requires an extraordinary knowledge of how both DOS and .BAT files work. 13.0 THE SECURITY FEATURES OF RBBS-PC -------------------------------------- RBBS has always been an open system designed for public use. A SYSOP should always ASSUME that EVERY FILE ON THE PC running RBBS-PC CAN BE DOWNLOADED AND/OR DESTROYED. However, RBBS-PC has extensive safeguards that systematically enhance security and privacy. For example, RBBS-PC has the logic within it's code to prohibit anyone (including SYSOP's) from downloading the RBBS-PC "system" files described in section 6.1. RBBS can still be run as a wide open system, but the SYSOP has many additional options to restrain access. These security options make RBBS much more suitable for private and business use. RBBS-PC's security is controlled by three things: 1. the system configuration file (RBBS-PC.DEF), 2. the two external security files for a. passwords (PASSWRDS), and b. file downloads (FILESEC), and 3. the users file (USERS) in which each user has an assigned security level. The users file is controlled by the SYSOP's user maintenance function 5 as described in section 14.1. To change a specific users security level you select the M>odify option and then the S>ecurity option. This allows you to set the security level for a user. Users cannot set their own security level. Section 13.3 describes how to implement special passwords that provide special privileges to the groups that issue them. Section 13.4 describes how specific files, groups of files, or even whole disk volumes can have download security levels associated with them. 13.1 RBBS-PC's Security Features -------------------------------- All users have a security level assigned to them. This is an integer in the range -32,000 to +32,000. There are then over 65,000 possible security levels. Each command in RBBS also has a security level assigned to it. Security assignments are controlled by the SYSOP. To use a command, the caller's security level must be at least as high as the command's security level. The SYSOP can assign a file or group of files both a security level and a password. To download a file, a caller must have a security level at Page 45 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 least as high as the file's and be able to give the file's password (if one is present). All users must pass these security tests, including anyone with SYSOP privileges. Messages can now be assigned a password by their creator. Then only persons who are able to give it can read or kill the message. Messages with password protection will show <PROTECTED> when scanned. Callers have no way of distinguishing messages to private individuals and to groups except by how they are addressed. Persons with SYSOP privileges can read all messages. Security violations are logged to the CALLERS file. These include attempting to use functions without sufficient security clearance, and failure to give required passwords. RBBS-PC's default configuration is that of an "open" system. RBBS-PC's security system provides the SYSOP with several choices on how he wishes to run his RBBS. The chief ones are as follows: 1. Change the bulletin board from an open system available to all callers, to a pre-registered system available only to specified users. To support this option, there is a function in the SYSOP's user maintenance option 5 to ADD users. 2. A SYSOP can set up different "classes" of users by assigning different security levels to different users. Concurrently the SYSOP would have to assign different security levels to different commands. For example new callers might be permitted only to leave a comment, read bulletins, and list files that can be downloaded. Or there might be a group of files assigned a security level that only members of a special interest group can download. 3. The SYSOP can segregate the functions of the bulletin board into different groups based on a password. A specific file or group of files can be downloadable only to those who knew the password. Similarly, messages can be made open to everyone knowing the password but closed to everyone else. This way there can be semi-private portions of the bulletin board. 13.2 Examples of Uses for RBBS-PC's Security System --------------------------------------------------- SPECIAL INTEREST GROUPS -- A special interest group (SIG) in a users group wishes to run a RBBS for both the general public and its own use. An example would be an author's SIG for persons interested in publishing books and articles or developing commercial software. A definite need would exist to be able to address messages to everyone in the SIG without making them open to every caller. The SIG would establish the convention to password protect general SIG messages with the password AUTHORONLY, and to address them to AUTHOR'S SIG. Another example would be a bulletin board devoted to the exchange of software. Allowing persons to use the message subsystem would only interfere with the primary purpose of the bulletin board. Therefore the SYSOP removes from the menu the functions for leaving and reading messages. In case a person requests the function even though it is not displayed, these functions are assigned a security level higher log onto the system longer than normally allowed. The SYSOP can set up the special password SOFTEXCHANGE, with a maximum time on of 150 minutes instead of the normal 30. By shifting over to this special password after logging in, members can get extra time if they need it. Page 46 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 SOFTWARE SUPPORT -- An author of a freeware program offers RBBS support to all persons who register their copy with him and send a contribution of $35. The registered user can get answers for problems and download free updates and sample applications. The author wants anyone to be able to call just to find out about the service. New callers get a security level of 2 automatically assigned to them. This allows them only to use the message subsystem. The file subsystem is assigned a security level of 7. Contributors are added by the SYSOP with a security level of 7 and a pre- assigned password. Except for SYSOP functions, registered users have free reign in the RBBS. CLIENT SUPPORT -- A SYSOP on a public RBBS also works as a management consultant. She has several associates who work with her on projects. She needs to be able to send and receive messages from her associates which the general public should not see. So they agree on a message password NOTPUBLIC. To support her different clients she also needs to leave private files for downloading. To each client she assigns a special downloading password. To restrict downloading to just that client, filenames are put in the file security file with the appropriate password. Only persons with the password can then download them. PRIVILEGED ELECTRONIC MAIL -- A company uses RBBS-PC to help support its regional offices. Only regional vice-presidents should be able to download certain management reports. In file security these reports are assigned a high security level of 9, which only managers get. 13.3 How to Implement the Password File --------------------------------------- Section 7.6.9 describes how the SYSOP can designate the name of the file containing the privileged group passwords to RBBS-PC. The SYSOP can use any text editor to create and update the file of privileged group passwords as it is a plain ASCII file. Put the information for each password on a single line and separate the fields with commas. It is important to note that EACH record of either the password or the file security file must contain THREE fields (i.e. two commas). For the password file, the format is: <password>,<security level>,<max time on>. Note: Time is in units of minutes. Two examples are: EXTEND,5,120 ,7,128 If you are using COPY CON to create this file you "MUST" press F6 at the end of the last entry prior to pressing carriage return. A user who issued the password change function and supplied the password EXTEND would have his security level temporarily set to 5 and be granted an elapsed time of 120 minutes for the current session (his elasped time per day would still be whatever was set in option 15 of CONFIG). A user who logged on with a security level of 7 would automatically be granted 128 minutes on the system. Page 47 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 13.4 How to Implement the Security for Download Files ------------------------------------------------------ Section 7.6.4 describes how the SYSOP can designate the name of the file containing the passwords and security levels that can be used to restrict downloads of specific files, volumes, or files names meeting certain "wildcard" criteria. This file contains file names with download restrictions in the format: <filename>, <security level>,<password> Note: Each line is a record and ends with carriage-return line-feed. The only field optional is the password field for a filename. By leaving the password field empty, no password is assigned to a file. The commas between the fields are necessary. YOU MUST HAVE TWO COMMAS ON EACH LINE even if you do not have a password associated with the file. Some examples would be: COMMAND.COM, 10, DOS PAYROLL.DAT, 99, BANKRUPT CALLGIRL.SEX,,ILLEGAL STOCKS,100, The file COMMAND.COM could not be downloaded unless a user had a security level equal to or greater than 10 AND could supply the password "DOS". The file PAYROLL.DAT could not be downloaded unless a user had a security level equal to or greater than 99 AND could supply the password "BANKRUPT". Any user could download the file CALLGIRL.SEX if he could supply the password "ILLEGAL". Any user with a security level of 100 or higher could download the file STOCKS without supplying any password. Additionally "wild-card" characters and drive designators can be used to protect or restrict certain classes of files (by extension, by drive, etc.) from being downloaded. Some examples would be: A:*.*,8, E:*.SEC,2,PW1 A*.M*,0,GX3 XY?X.*,9,3XG All files on drive A would require the users to have a security level of 8 in order for a user to download them. Any user who wanted to download a file whose extension was ".SEC" and was found to be on drive E would have to not only have a security level of at least 2 but to also give the password PW1. The third entry above would require a user who wanted to download any file on any drive with a prefix that began with "A" and an extension that began with "M" to have a security level of at least 0 and to enter the password GX3. Finally, the last entry above would require any user who wanted to download any file on any drive whose four letter name began with "XY" and whose last letter was "X" with any extension to have a security level of at least 9 and enter the password 3XG. To get exceptions to the general rule, just put the exceptions first. RBBS-PC's file security search stops with the first applicable entry that it encounters. For example, 1. if you want all files on the B drive to require the user to have a security level of at least 3, Page 48 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 2. except that files on the B drive with the extension ".SEC" would require the user to have a security level of at least 6, and, 3. regardless of the disk drive that they were on, any file beginning with "MES" with an extension of ".SEC" would require the user to have a security level of at least 12 you would enter the following into the file security file MES*.SEC,12, B:*.SEC,6, B:*.*,3 Special Note: RBBS is hard coded so that there are some files that nobody can download -- not even the SYSOP. These are RBBS-PC.DEF, users, messages, callers, group password, comments, the file security, and backup files. Similarly the batch files that control RBBS and let the caller exit to DOS 2 can not be downloaded. The default security file provided with RBBS-PC is empty. 13.5 How to Implement the Security for RBBS-PC Commands -------------------------------------------------------- RBBS-PC allows each command to be assigned it's own security level. A user who wishes to invoke an RBBS-PC command must have at least the same security level as the command. Let's assume that a SYSOP wants to set up the following classes of users: Classification of Users Security Level "Locked Out" Users 0 New Users (first time) 1 Normal Users 2 Users that can "view" a Conference 3 Users that can enter Messages 4 Users that can download files 5 Users that can upload files 6 Users that can Join a Conference 7 Users that can do some SYSOP commands (Jr. SYSOP's) 8 Users that can enter a "door" 9 Users that can enter all SYSOP commands (Co-SYSOP's) 10 Page 49 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 The following table illustrates one method of assigning each RBBS-PC command it's own security level: Subsystem/Command Security Level Assigned to Command Messages Subsystem B>ulletins.......................... 1 C>omments........................... 1 D>oor subsystem..................... 9 E>enter message..................... 4 F>iles system....................... 1 G>oodbye............................ 0 H>elp............................... 1 I>nitial welcome.................... 1 J>oin a conference.................. 7 K>ill messages...................... 4 L>ines per page..................... 1 O>perator page...................... 1 P>ersonal mail...................... 2 Q>uick scan of messages............. 1 R>ead messages...................... 2 S>can messages...................... 1 U>tilities (more)................... 1 V>iew a conference.................. 3 W>ho's on other nodes................3 X>Expert on/off..................... 1 ?>Functions......................... 1 Utilities Subsystem B>aud rate.......................... 1 C>ase change........................ 1 F>ile transfer protocol............. 1 G>raphics........................... 1 H>elp............................... 1 L>ine feeds......................... 1 M>sg Margin......................... 1 N>ulls.............................. 1 P>assword........................... 2 Q>uit to messages subsystem......... 0 R>eview preferences................. 0 S>tatistics......................... 1 T>ime............................... 1 U>serlog............................ 2 X>Expert mode toggel................ 1 !>Prompt Sound...................... 1 Files Subsystem D>ownload........................... 5 G>oodbye............................ 0 H>elp............................... 1 L>ist file directories.............. 7 N>ew files.......................... 6 Q>uit to messages subsystem......... 1 S>earch directories for string ..... 1 U>pload a file...................... 6 X>Expert mode toggle................ 1 ?>file transfer information......... 1 Page 50 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 SYSOP Subsystem 1>List comments..................... 8 2>List callers log..................10 3>Recover a Message................. 8 4>Erase comments.................... 9 5>USERS maintenance.................10 6>Toggle page bell.................. 8 7>Exit to DOS 2.x or above.......... 9 13.6 Beware of the "Trojan Horse!" ----------------------------------- Despite RBBS-PC's security always remember that you should always assume: "EVERY FILE ON THE PC RUNNING RBBS-PC CAN BE DOWNLOADED, MODIFIED, AND/OR DESTROYED!" RBBS-PC's security system appears to be so fool-proof that some individuals have resorted to uploading programs that appear to do one thing, but actually do something else. These "trojan horse" programs search all the disks that are connected to the PC that the program is running on for such RBBS files as RBBS-PC.DEF or USERS. The program then copies these files to an innocuosly named file that can be downloaded later when the person who uploaded it logs onto the system again. Since RBBS-PC.DEF contains the pseudonym that the SYSOP can use to logon on remotely as the SYSOP, once the user downloads his copy of it he can log on as the SYSOP and do just about anything including exiting to DOS and formatting all the disks on the system. Similarly, the USERS file contains passwords and the security levels of everyone on your RBBS -- some of whom may have SYSOP privileges. You can protect yourself against the former by not allowing anyone to logon as you (i.e. the SYSOP). To do this read section 7.1 regarding parameters 3 and 4. You can protect yourself against the later by simply not allowing any user to have SYSOP privileges. Of course there is the "trojan horse" program that doesn't even bother with the above, but simply destroys all the disk files on all the disks that are connected to the PC that is running the program. Read section 17.0, Uploaded File Tips, regarding how you can protect yourself against such programs. 14.0 SYSOP FUNCTIONS ------------------- The SYSOP functions are not available to the general user, and it should be noted that the SYSOP should not use some of the user functions either because the code will not work right if called from the main console, or the function is not for use by the SYSOP. Such functions are the <O>perator, <N>ewbaud, <PW> password, and file upload/download using XMODEM. File download using ASCII can be used to "type" files available for download so they scroll across your screen. To enter the SYSOP mode press the ESC key locally or enter the special 'pass' and 'word' first and last name from a remote terminal. 14.1 SYSOP Commands Within RBBS-PC ---------------------------------- The following operations can then be performed by entering a number only at the command prompt: 1 - Type comments file. The contents of the COMMENTS file is displayed. This file can also be inspected using a TYPE command from DOS. It is a ASCII sequential text file. Page 51 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 2 - Type CALLERS file. A log is maintained of all persons who have called the system. This function will list the file showing the users name and the date and time signed on as well as the files he upload/downloads along with any security violation or errors encountered. This is a random access file of 64 byte records. 3 - Resurrect a message. This function will return a message that has been killed to an active state. If message file has been "packed", the killed messages are no longer recoverable. The function will ask for the message number to be recovered. 4 - Erase the comments file. This function will erase the comments file by killing the file. Since the file is opened "APPEND" a new comments file will be created the next time a user leaves a comment. 5 - USERS file maintenance. The users file contains entries for each user registered with the system. This function permits the SYSOP to list the file on the display, print the file on the printer (LPT1:) or to perform limited editing of the user file records. In <M>odify mode the following subfunctions are available: A - Add a user to the USERS file. M - Return to the <M>ain menu or function prompt. P - Toggle the printer flag to print entries on the printer. N - New password. Permits the SYSOP to change the password for the user. F - Find User. Permits the SYSOP to locate a user by entering the users name. S - Set the security level of the user. This can be used to lockout or grant special privileges to the user. In <M>odify mode a record will be displayed followed by a subfunction prompt for action. To get to a specific record the record number can be entered at the prompt and if valid that record will be displayed. If the record number is invalid or an empty c/r is entered then the next record in the file will be displayed. 6 - Toggles the operator page bell on/off and overrides the "office hours" specified in the RBBS-PC.DEF file. 7 - If the SYSOP has logged on remotely and is running on DOS 2.0 or greater, this function will dynamically setup a batch file to assign the SYSOPS terminal as the main console. It then returns to DOS and if a. RBBS was invoked via a batch file, and b. that batch file is checking for the batch file which RBBS-PC dynamically builds for option 7, and c. the batch file that invokes RBBS-PC executes the batch file that RBBS-PC dynamically builds for option 7, then the SYSOP will see the DOS prompt at his terminal and can execute whatever DOS command or program supported by the CTTY command. DOS will look for COMMAND.COM to be present on the disk drive your system booted from since this option loads in a copy of COMMAND.COM to run under the copy that is running RBBS-PC. Also be sure to read section 15 and make sure that you THOROUGHLY understands the limitations that DOS places on you when this option is invoked. Page 52 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 Two areas of caution are advised when using option 7 under DOS 2.0 or above. First, each SYSOP should test what he can do remotely. Software that directly reads and writes to the video BIOS and does other things that bypass the standard input and output of DOS simply won't function correctly. Second, you should be aware that you are in DOS and can only return to RBBS by issuing the EXIT command. This will return to the dynamically built batch file that was built by RBBS-PC. This file will then continue executing and is designed to reassign the keyboard as the console and then re-invoke RBBS-PC. If you get disconnected while in DOS, you system will be locked up. The console will be assigned to your communication port and your Hayes modem will have dropped the line and will have been set not to auto-answer. The only way to re-boot the system is a manual power on/off sequence. 14.2 SYSOP's Use of Function Keys --------------------------------- The following function keys (ten keys on left side of keyboard) are designed to give the SYSOP special local controls that can be actuated without entering the SYSOP mode (using the ESC entry key). The current status of function keys F3, F4, F6 and F7 are displayed on line 25. F1 - Return to DOS. This will terminate a session if a caller is on-line. F2 - Return to BASIC. This will also terminate a session. This returns to DOS under the compiled version. F3 - Printer toggle on/off. This changes the printer on-line status. When on-line the printer will print callers names and file names uploaded/downloaded. It will also print all error messages except the ERROR 68 used to check that a file exists. This function should match the condition of the printer. If the printer is going to be left off, the PRINTER toggle should be left off. When the printer toggle is on "LPT" will be displayed in positions 8-11 of line 25. F4 - Operator page toggle. This changes the status of operator annoy and records the change in the "node" record associated with the copy of RBBS- PC associated with function key 4. This is set by the CONFIG program parameter # 7 which establishes the SYSOP's office hours. This can be used to override and extend the "office hours" set up by CONFIG.BAS. When the operator annoy toggle is on "ANY" will be displayed in positions 5-7 of line 25. F5 - Forces a ring back system to answer the phone. F6 - SYSOP available. This changes the status of operator available and records the change in the "node" record associated with the copy of RBBS- PC associated with function key 6. This is useful if during your "office hours" you don't wish to be disturbed temporarily. When the sysop available toggle is on "AVL" will be displayed in positions 1-3 of line 25. F7 - SYSOP gets control of the system after current user logs off. When the sysop next toggle is on "SYS" will be displayed in positions 13-15 of line 25. F8 - Allows the SYSOP to grant an on-line user temporary SYSOP privileges. This is a toggle on/off switch. F9 - SNOOP toggle. This changes the SNOOP from the default value the first time it is pressed and toggles it on/off thereafter. SNOOP off clears the screen and turns the cursor off. It also keeps the download beeps from Page 53 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 sounding. The SNOOP should be left off for normal use to keep the system startup screen from "burning into" the monitor. If the SNOOP is left on, the monitor should be physically turned off except when you are observing the RBBS in action. Leaving the monitor off will not affect performance of the RBBS. F10 - This is the forced chat switch. It announces your forced chat and who you are before turning the keyboard over to you and the caller. Along with the ESC key (which ends the chat mode) this is the same key you use to answer a page. The SYSOP can also enter commands on the command prompt line while a caller is on-line. The command entered will cause the system to respond just as it would had the caller entered the command. This should be used with caution because it could confuse a new system user -- users are often timid enough without knowing that big brother is actually watching them! Let the caller page you then tell him that you can assist with commands if he gets into trouble. 15.0 DOS LIMITATIONS ON RUNNING PROGRAMS REMOTELY ------------------------------------------------- 15.1 How to Get DOS to Monitor Carrier Detect --------------------------------------------- When accessing your PC via a communications port, the carrier detect signal tells the PC that you are on-line. DOS's major limitation is that there is no way to tell DOS to automatically monitor carrier detect when the standard input and output is transferred to a communication port (i.e. via the CTTY command). RBBS-PC makes sure that the carrier is not dropped when a user exits to DOS either via the "DOORS" option or using the remote SYSOP function 8. However, it is the SYSOP's responsibility to insure that whatever program(s) are invoked after leaving RBBS-PC performs all the necessary functions to maintain the communications session and, when exiting to return to RBBS-PC, insure that the carrier is "NOT" dropped. Most application programs (i.e. databases, etc.) are not designed to be controlled by a user accessing it from a communications port. This problem is solved when a function is invoked that: 1. Checks to see if the standard input and output console have been assigned to an auxiliary console such as a communication port. 2. If condition 1 is true, checks to see if the carrier detect signal is lost by intercepting each interrupt from the communication port the auxiliary console has been assigned to. 3. If BOTH conditions 1 and 2 are true, this function would cause DOS to switch back to the standard screen and keyboard for its operations AND then continue processing whatever batch file that had been executing (if one was). Such a function (or device driver) would provide a "fail safe" feature that would allow users to exit RBBS-PC to use whatever other software the SYSOP chose to make available (i.e. relation databases for complex inquiries -- bibliographic, sports, games, etc.). For those anticipating using RBBS-PC's "doors" or exiting to DOS when you are a remote SYSOP, you are strongly encouraged to consider using the "watchdog" utility program available on many bulletin board systems under such file names as WATCHDOG.COM, WATCHDOG.ASM, WATCHDOG.DOC, WATCHDOG.EXE that monitors the communication port for you and reboots your system if carrier drops. If you don't use a program like WATCHDOG and accidently hang up Page 54 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 while in a "door" or in DOS, you system will remain "hung" until you can manually reboot it. If you aren't technically inclined and want to use RBBS-PC "doors", I suggest you consider using MultiLink from The Software Link, Incorporated at (404) 998-0700. While MultiLink costs about $500 and neither the CPCUG's nor RBBS-PC authors have any connection with it, it does provide a mechanism for overcoming DOS's inability to have programs invoked from remote users (release 2.0.6 or higher of MultiLink is required). If RBBS detects MultiLink is present when a user exits to DOS via "doors", RBBS-PC automatically passes control of the communications port that the user is on to MultiLink so that MultiLink can do the carrier monitoring on behalf of the application. 15.2 How to Redirect Graphic Displays to Remote Users ------------------------------------------------------ Programs that utilize the PC's built in video memory (such as the IBM BASIC interpreter or WordStar when it writes to the 25th line) need to have such I/O redirected in a special way to a remote users terminal. Additionally, if the I/O is redirected to the communications port, the terminal on the other end must have a "cursor" that can be sent the appropriate command sequence to move it around on the remote users terminal as necessary. Without this capability, programs made available through "doors" must be line-at-a-time programs. This of course excludes programs such as WordStar, Lotus/123 etc. If you aren't technically inclined and want to use RBBS-PC "doors" for applications that write directly to the PC's video hardware, I suggest you consider using MultiLink (see section 15.1). MultiLink provides a mechanism for overcoming DOS's inability to redirect graphics to remote users. If RBBS detects MultiLink is present when a user exits to DOS via "doors", RBBS-PC automatically passes control of the communications port to MultiLink and notifies MultiLink of the kind of MultiLink-supported terminal to redirect the application's graphics to (presumably one with a controllable cursor). 16.0 CONFERENCING WITH RBBS-PC ------------------------------- RBBS-PC is intended to be an open system. The "conference" concept is one that allows either anyone who can leave messages (i.e. a "public" conference) or a pre-registered set of users (i.e. a "private" conference) to engage in a specialized dialogue. To make a "conference" successful several guidelines should be followed rather rigorously: 1. Establish a "conference chairman" (i.e. a SIGOP). This is the "policeman" of the conference. His job is to add new users, delete old ones, make sure the subject and/or the agenda of the conference is adhered to by killing messages that are inappropriate. 2. Establish an "agenda" or list of subject areas for the conference. One of these should be new subject areas. These areas should be VERY narrow in scope. The essence of any good conference is keeping it focused. Everyone has been in at least one meeting/conference that was a waste of time because whoever was running the meeting/conference did not keep the dialogue centered on the subject or agenda. The SYSOP sets up a conference using CONFIG.BAS to pre-format up to two files -- one for the messages to be associated with the conference and one for the users to be associated with a conference (if it is a "private" conference). The file name for a "conference" can be any seven characters Page 55 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 that are valid for a file name. The eighth character must be a "M" (for the messages file associated the conference) or a "U" (for the users file associated with the conference). The SYSOP then can chose to enter the conference member names in the conference USERS file by using the SYSOP function 5. The SYSOP can "join" any conference and need not be in the particular conference USERS file. To set up a conference chairman, the SYSOP need only 1. "Join" the conference, 2. Use SYSOP function 5 to enter the users name who is to be the conference chairman into the conference's USERS file. 3. Set the users security level in the conference's USERS file to a security level that can issue the SYSOP function 5. This will allow the conference chairman to add users. Remember when a user joins a conference he must already be registered in that conference's USERS file. If he isn't, he can only "view" the conference. When someone issues the J>oin command to join a conference, his standard security level is temporarily superseded by the security level associated with his user name within that conference's USERS file. For example, normal user might be given the security required to add users to the conference USERS file for a particular conference since he is the conference chairman. When he joins the conference of which he is chairman, his normal security is bumped up so that he can add users to the users file of the conference. When he exits that conference, his security level is returned to normal. If he should subsequently join another conference of which he is not chairman, he would find he could not add users to that conference's users file. Other than a conference chairman, none of the conference members should be given any higher security than they otherwise enjoy as a regular RBBS-PC user. There are no limits on the number of conferences within RBBS-PC. Here are some examples of some conference names: Conference Name Name of Message File Name of Users File for that Conference for that Conference (if it's "private") FORSALE FORSALEM.DEF FORSALEU.DEF GAMES GAMESM.DEF GAMESU.DEF FINANCE FINANCEM.DEF FINANCEU.DEF SYSOPS SYSOPSM.DEF SYSOPSU.DEF CLONES CLONESM.DEF CLONESU.DEF RELIGON RELIGONM.DEF RELIGONU.DEF PHILOSP PHILOSPM.DEF PHILOSPU.DEF BBS BBSM.DEF BBSU.DEF If a continuity of dialogue is to be achieved, it is advisable to keep the conference "focused" either by keeping the number of conference members limited to thirty persons or less or by keeping the subject matter very narrow (i.e. the IBM PC's 30MB disk size limitation). Another interesting thing about "private" conferences as implemented within RBBS-PC is that it they are not "public" and, therefore, are even more protected by the first, fourth, and fifth amendments. Page 56 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 17.0 UPLOADED FILE TIPS ----------------------- If someone uploads a BASIC file to you, and it will not list on your screen using the DOS TYPE command, you should go into BASIC, load the file, list it, then resave it using the same name. If you get a `Direct Statement In File' error printed on the screen when you load the file, that means that you downloaded a text statement with the file (one that has no line number, one that was edited on a word processor which created a carriage return without a linefeed -- thus overwriting two lines and giving the appearance of a direct statement in the file). This will not interfere with the resaving of the file unless the direct statement is at the beginning of the file; if the file lists ok, then the direct statement is at the end of the file. If the file does not list properly, then the direct statement is at the beginning of the file and has to be removed using a text editor (EDLIN) before the program can be loaded and run. Do not attempt to save a BASIC file after getting the `Direct Statement In File' error during loading without listing the program first; you will destroy the file otherwise. If you wish to load an uploaded file (a BASIC program or any other text file) into a text editor to change the content of the file, you will have to first add line feeds to the end of each line (after each carriage return). Finally, every SYSOP should assume that any file uploaded to him that can be executed (i.e. .BAS, .COM, .EXE) has the capability of destroying all the files available to the PC it is executed on. This may be because the documentation is in error, the program was executed incorrectly, or the program was designed to be malicious. It behoves every SYSOP to know what every file uploaded to him does in order to protect not only himself, but his users. 18.0 COMPILING AND LINKING RBBS-PC ---------------------------------- RBBS-PC CPC12-5B's source is distributed along with the executable program RBBS-PC.EXE. It is NOT necessary for anyone running RBBS-PC to recompile or re-link RBBS-PC in order to utilize RBBS-PC. However, some users may wish to modify the source and recompile it. This section is intended for those hardy few who choose to do so. Remember only what is distributed is supported -- anything else is strictly yours to debug! 18.1 Compiling CONFIG.BAS and RBBS-PC.BAS ----------------------------------------- Because of the size of the CONFIG.BAS (version 1.8) the BASIC compiler command should be: BASCOM CONFIG.BAS,, /E/S/O; The output will be CONFIG.OBJ with a size of about 150,221 bytes. Similarly, because of the size of the RBBS-PC.BAS (version CPC12) the BASIC compiler command should be: BASCOM RBBS-PC.BAS,, /E/C:4096/S/O; The output will be RBBS-PC.OBJ with a size of about 168,565 bytes. 18.2 LINKing CONFIG ------------------- CONFIG.OBJ can be LINKed to produce CONFIG.EXE with the command Page 57 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 LINK CONFIG+IBMCOM,CONFIG.EXE,,C:; assuming that all the required files are on the C drive. The output will be CONFIG.EXE with a size of about 103,168 bytes (or about 101K). 18.3 LINKing RBBS-PC Without MNP File Transfer Protocol ------------------------------------------------------- MNP file transfer protocol is NOT required to be included in RBBS-PC (see CONFIG's option 31). Therefore, RBBS-PC can be LINKed using the standard IBM DOS LINKer and without including the MNP library. To do this enter the command: LINK RBBS-PC+IBMCOM+UTILIT+BDRIVEC2+PC-NET,RBBS-PC.EXE,,C:; assuming that all the required files are on the C drive. The output will be RBBS-PC.EXE with a size of about 109,184 bytes (or about 107K). 18.4 LINKing RBBS-PC With MNP File Transfer Protocol Capabilities ----------------------------------------------------------------- Microcom's error-free protocol, MNP, is available AS AN OPTION for file transfer beginning with version CPC12-4A of RBBS-PC. The RBBS-PC.EXE file that is distributed includes code from the MNP library. The MNP library file provided with RBBS-PC is done so under the following condition: "The MNP library file provided with RBBS-PC is the exclusive proprietary property of Microcom, Inc. and this copyrighted program material is supplied by Microcom exclusively for use with the RBBS-PC bulletin board system. Inclusion of library code within RBBS-PC does not in any way grant a license to the Microcom Networking Protocol (MNP). The use of the RBBS-PC MNP library code modules or MNP in any product other than the RBBS-PC program is a violation of Microcom's proprietary rights in the MNP technology." Because the Microcom library code was generated by the Lattice C compiler, the standard LINKer that IBM provides with PC-DOS can't be used. This is because the Lattice C compiler makes assumptions about how data segments are loaded in memory that are incompatible with the way the IBM LINKer handles the object code generated by the IBM BASIC compiler. Therefore to include MNP file transfer protocol a linkage editor which allows the specification of the order in which segments within the class of "DATA" must be used. One such linkage editor is Plink-86 from Phoenix Computer Products Corporation (1416 Providence Highway, Suite 220, Norwood, MA 02062). The Plink-86 linkage editor can be invoked by setting up a file called PLINK.DTA with the following following PLINK-86 commands in it: FILE RBBS-PC,IBMCOM,UTILITY,BDRIVEC2,PC-NET,RBBSMNP CLASS CODE CLASS INIT CLASS DATA CLASS RT_DATA CLASS BLANK CLASS CONST LIBRARY BASCOM,MNP LIBRARY BASCOM,MNP OUTPUT RBBS-PC; Page 58 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 The above assumes that the following files are on the default disk drive: RBBS-PC.OBJ IBMCOM.OBJ UTILITY.OBJ BDRIVEC2.OBJ PC-NET.OBJ RBBSMNP.OBJ BASCOM.LIB MNP.LIB The output will be RBBS-PC.EXE on the default disk drive with a size of about 141,296 bytes (or about 138K). 19.0 LIMITED LICENSE -------------------- The software is copyrighted but A LIMITED LICENSE IS GRANTED and you are free to use and share it under the following conditions: 1. You may NOT distribute RBBS-PC in modified form. 2. You may NOT charge a fee for RBBS-PC itself, and 3. You MUST retain all references to the copyright and authors. Please distribute the original version (or update thereof) of the program. If you have changes either add a new file with that copy or supply a file to be MERGED with the original to create it. This is done so that future revisions can be easily added to the system without requiring the entire program. Please do NOT resequence the program. All revisions will be as files that can be MERGED with the base program or update thereof to incorporate the new fixes and enhancements. 20.0 LIMITED WARRANTY --------------------- The RBBS-PC CPC12 program is provided "as is" without warranty of any kind, either expressed or implied, including, but not limited to the implied warranties of merchantability and fitness for a particular purpose. The entire risk as to the the quality and performance of the program is with the user and should the program prove defective the user and not the authors will assume the entire cost of all necessary remedies. None of the authors warrant that the functions contained in the program will meet any users requirements or that the operation of the program will be uninterrupted or error free. In any case, each author's entire liability will be limited to the total amount of money the individual user paid directly and explicitly to each author for the use of RBBS-PC. 21.0 UPGRADING FROM CPC12-3B TO CPC12-5B ---------------------------------------- Because RBBS-CPC12-5B requires that the USERS file be reformatted, you must perform the following steps to migrate from CPC12-3B to CPC12-5B: 1. "Pack" your CPC12-3B USERS file using CONFIG Version 1-6. 2. Run the one-time only utility FUSR124A.BAS. 3. Rename all directories (i.e. DIR99 renamed to 99.DIR). 4. Rebuild your USERS file (even if upgrading from 12-4B). PLEASE NOTE!!!!! ---- CPC12-5B has a new CONFIG.BAS (version 1.8) that Page 59 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 replaces the older versions of CONFIG.BAS and the .DEF files that they created! 22.0 RBBS-PC FUTURE DIRECTIONS ------------------------------ RBBS-PC CPC12 can be a lot of fun to operate and can be a useful tool for information exchange. Pass copies of it along to others, so more of these systems will spring up all over the country! RBBS-PC seems to be meeting a need within the IBM-compatible PC user community. As you can see from the brief history of RBBS-PC CPCxx.x outlined in section 1.3, it has had a rapid evolution in the past year of it's existence. However, there are some future directions that I see for it and I would like to share them with you. RBBS-PC REDESIGN -- On June 18, 1985 IBM announced a new IBM Personal Computer BASIC Compiler 2.0 and it has been available since the third week in July of 1985 at an unconscionable list price of $495. Microsoft's QuickBasic compiler has been available since August 2, 1985 with a list price of $99. QuickBasic is 100% compatable with the IBM Version 2.0 BASIC compiler with two exceptions -- QuickBasic does not support arrays greater than 64K or ISAM files. CPC12-5B will be the last version that functions under the IBM BASIC interperters and IBM's BASIC compiler Version 1.0. Because of the additional features that are in these two new BASIC compilers, the next version of RBBS-PC (CPC13-1A) will be converted to and be compilable by these two new compilers. However, only the RBBS-PC.EXE file generated by the QuickBasic compiler will be tested. Hopefully, the RBBS-PC source code can be uncompressed so that there is only one BASIC statement per line and that comments can be added to the source code. No one wants comments back in the source code more than I do! There are sections of the currently uncommented code that I have had to re-figure out four and five times -- each time I had to make a change to it. Hopefully, the new compiler will allow the RBBS-PC source code to be both fully commented and uncompressed. Regretably this may preclude RBBS- PC from executing under the BASIC interperter until a new BASIC interperter becomes available that supports the new compiler. ADDITIONAL PROTOCOLS -- there is at least one additional protocol that should be added to RBBS-PC. It is one that makes use of CRC16 (cyclic redundancy check). A "public domain" one exists for the IBM PC and is implemented in Hayes' SMARTCOMII. One SYSOP has already told me he is working on adding that to RBBS-PC. NATIONAL ANNUAL MEETING OF SYSOP'S -- As PC's (IBM's and others) become more common in homes and offices, there use as vehicles for information exchange will grow. Indeed, the growth of RBBS-PC has been astounding! An annual meeting of SYSOP's could foster this growth, the exchange of information, assist in focusing on the issues (regulatory and otherwise) that foster/inhibit this growth, and act as a forum for new ideas. A national meeting, perhaps sponsored by the Capital PC User Group, and initially funded by the major PC manufacturers (Apple, IBM -- are you listening), valued added network suppliers (MCI, Telenet -- don't miss this untapped market), and the major modem manufacturers (Hayes, Rixon, Racal- Vadic) could be held in Washington in 1985 (at the FCC). The RBBS-PC SYSOPS are not found in the big corporations -- the Fortune 500 have their super mainframes. It is in the millions of small businesses, non-profit associations, educational institutions that the RBBS concept has found a home. As I expect most who would attend would be paying their own way, Page 60 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 the first conference would probably consist of that small "band of brothers" who have set up boards out of the intensity of their own commitment. If you are with a manufacturer that might be interested in sponsoring such a meeting in 1985, work with your organization to make it happen! If in the normal course of your business contacts you see a potential sponsor of such a conference, persuade them to look into sponsoring it. My own vision of such a conference is sort of a 1980's electronic "Woodstock" -- if for no other reason because of the very "volks" nature of SYSOPS. It has been a long time since Washington, D.C. has had a conference "of the people, by the people, and for the people." If you are interested, drop me a line here in Great Falls, Va. These are only just a few of the ideas that come to mind for RBBS-PC in August of 1985. It will be interesting to see how it evolves. Page 61 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 APPENDIX A -- RBBS-PC Record Formats ------------------------------------ This appendix is intended to document the record formats of some of the more significant records used within RBBS-PC. As such it is intended more as a "programmers guide" for those who wish to write RBBS-PC utilities rather than as "user documentation." No record format is "sacrosanct" and may change in future releases. However such changes are not done capriciously and, when they are done, are accompanied by some utility program that will allow the old files to be reformatted into the new format. The MESSAGES file contains the messages that have been left on RBBS-PC. It is a random file with 128-byte records. The first record of the MESSAGES file acts as RBBS-PC's "checkpoint" record. The records immediately following this first record are the RBBS-PC "node" records. Each "node" record represents the activity/options associated with a particular copy of RBBS-PC ("node"). There can be up to nine copies of RBBS-PC running simultaneous sharing the same set of static files and therefore there can be up to nine "node" records following the "checkpoint" record. The MESSAGES file has the following logical format: +----------------------------------------------+ Record #1 | RBBS-PC "checkpoint" record | +----------------------------------------------+ Record #2 | RBBS-PC "node" record for node # 1 | | | | up to | | | | RBBS-PC "node" record for node # 9 | +----------------------------------------------+ | First Record in Message portion of file | +----------------------------------------------+ | | \ Message records that have been used \ \ \ | | +----------------------------------------------+ | Record available for next message | +----------------------------------------------+ | Last record available in MESSAGES file | +----------------------------------------------+ Page 62 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 The FIRST RECORD of the "MESSAGES" file acts as a "checkpoint" record for all the multiple RBBS-PC's that may be sharing the MESSAGES and USERS files. It contains information critical to maintaining the integrity of these two files. The layout of RBBS-PC Message File Record Number 1 is as follows: Position Length Name Description 1 - 8 8 LE Number of last message on system 9 - 10 2 --- RESERVED FOR FUTURE USE ---- 11 - 20 10 CJ Current caller number 21 - 51 31 --- RESERVED FOR FUTURE USE ---- 52 - 56 5 Record Number of first record in the USERS file 57 - 61 5 NUR Record Number of the next available record in the USERS file 62 - 66 5 HUR Record Number of the last record in the USERS file 67 1 Reserved for Node ID currently reserving the USERS file 68 - 74 7 FMR Record Number where "messages" portion of the MESSAGES file begins 75 - 81 7 NMR Record Number of the next available record in the MESSAGES file where the next message may be written 82 - 88 7 HMR Record Number of the last record in the MESSAGES file 89 - 95 7 ME Maximum number of messages allowed in the MESSAGES file 96 - 97 2 Reserved for Node ID currently reserving the MESSAGES file 98 -126 29 --- RESERVED FOR FUTURE USE ---- 127 -128 2 MNDODES Maximum number of RBBS-PC's sharing this MESSAGES file As a programming reference, line 23000 of the BASIC source code for RBBS- PC.BAS contains the code for reading this "checkpoint" record. Page 63 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 Following the first record of the MESSAGES file are from one to nine "node" records. Each "node" record contains information critical to the running of that copy of RBBS-PC associated with that "node". The layout of each RBBS-PC "node" record is as follows: Position Length Name Description 1 - 31 31 NAM$ Name of last person on this copy of RBBS-PC 32 - 33 2 AVA Available indicator for SYSOP 34 - 35 2 AC Annoy indicator for SYSOP 36 - 37 2 SG Indicator that the SYSOP is next on the system 38 - 39 2 LH Line printer available indicator 40 - 41 2 WI Window's availability indicator 42 - 43 2 BE Eight bit transmission indicator 44 - 45 2 BPS Baud rate. -1 = 300, -2 = 450, -3 = 1200, -4 = 2400 46 - 47 2 UC Upper case indicator 48 - 52 5 TR! Time remaining on the system 53 - 54 2 GR Graphics indicator 55 - 56 2 SH SYSOP indicator 57 1 Activity indicator (I=inactive, A=active) 58 -128 71 ---- RESERVED FOR FUTURE USE ---- As a programming reference, review lines 175, 844, 13549, 43070, AND 44000 of the BASIC source code for RBBS-PC.BAS to see how these fields are set/used. A message within the messages file consists of a MESSAGE HEADER followed by the text of the message. The RBBS-PC Message File "message header" record layout is as follows: Position Length Name Description 1 1 Contains an "*" for read-only messages, blank otherwise 2 - 5 4 MT$ Message number of this message 6 - 36 31 FI$ The name of the person the message is from 37 - 57 21 T$ The name of the person to whom the message is sent 58 - 65 8 Time of day that the message was sent (HH:MM:SS) 66 - 66 1 Blank 67 - 75 9 D$ Date the message was sent (MM-DD-YY) 76 -100 25 SUB$ Subject of the message 101 -115 15 PAS$ Password for the message (if any) 116 -116 1 "Active" message indicator = hex 225 "Killed" message indicator = hex 226 117 -122 6 N$ Number of 128-byte records for this message -- including the the "message header" record. 122 -128 7 ---- RESERVED FOR FUTURE USE ---- Page 64 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 Each record following the MESSAGE HEADER record is a MESSAGE TEXT record and consists of 128 characters. Each of these 128-byte message text" records contains the message text. The end of each line in the message is followed by an RBBS-PC "end-of-line" indicator which is equal to a hexadecimal 225. This allows RBBS-PC to "pack" multiple message lines in a single 128-byte record. The USERS file contains information that is unique to each RBBS-PC user that logs on. It is a random file with 128-byte records. The layout of each users record within the USERS file is as follows: Position Length Name Description 1 - 31 31 N$ Users first and last name (separated by a blank). 32 - 46 15 PW$ Users password for logon. 47 - 48 2 SL Users security level (permanent). 49 - 62 14 OP$ Users logon options (see detail breakdown below). Length Name Description 49 - 50 2 TGA Number of times the user has logged on 51 - 52 2 LO Last message number read by the user 53 1 LG$(20) Protocol Preference (X, A, M, blank) 54 1 GR Graphics 0-text, 1-graphics, 2-color 55 - 56 2 MQ Margin length for this users messages 57 - 58 2 Bit Flag -- this 16-bit field is denoted by bit 0 being the least significant (i.e. right-most bit) and bit 15 being the most significant (i.e. left- most bit). These "bit flags" have the following meanings (0=off, 1=on): BIT Definition 0 Bell prompts 1 "Expert" mode 2 Nulls 3 Upper case only 4 Line feeds 5-15 RESERVED FOR FUTURE USE 59 - 60 2 ------- RESERVED FOR FUTURE USE --------- 61 1 PL Page length to use for this users terminal 62 1 ------- RESERVED FOR FUTURE USE --------- --- 14 63 - 86 24 CS$ City and state from which the user is calling. 87 -105 19 MA$ Machine the user is utilizing to call RBBS-PC. 106 -119 14 TD$ Date and time user was last on (MM-DD-YY HH:MM). 120 -122 3 LND$ Date user last listed a directory. 123 -124 2 UDL$ Number of downloads done by the user. 125 -126 2 UUL$ Number of uploads done by the user. 127 -128 2 ET$ elapsed time the user was on for day of last access. As a programming reference, line 9400 of the BASIC source code for RBBS- PC.BAS contains the code for opening this file. Page 65 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 APPENDIX B -- RBBS-PC Vendor Protocol Interface Specifications -------------------------------------------------------------- Before calling the vendor's protocol handling routine RBBS-PC will perform the following: 1. verify that the file exists if the file is to be downloaded. 2. verify that the file name requested is valid if the file is to be uploaded. 3. pass the communications port to the vendor's protocol handling routine with the file opened and carrier detect on. RBBS-PC will call the vendor's protocol handling routine as a standard call from the IBM BASIC language that has been processed by the IBM BASIC compiler. Hence the protocol handling routine can expect to receive/return a parameter list as generated by the IBM BASIC compiler. The call to the vendor's protocol handling routine, XYZ, is as follows: CALL XYZ(IM,F$,CP$,BPS) Where these four parameters have the following meanings: IM -- an integer indicating the direction of the file transfer. The values are: 1 -- download (from RBBS-PC to caller). 2 -- upload (from the caller to RBBS-PC). NOTE -- IM is utilized by the vendor's protocol handling routine to indicate the results of the file transfer. When the vendor's protocol handling routine returns to RBBS-PC it sets IM as follows: 1 -- file transfer successful 2 -- file transfer unsuccessful F$ -- a string which fully specifies the file name to be used in the file transfer. File names are limited in length to 40 bytes and the standard IBM file naming conventions. Files with extensions of .COM, .OBJ, or .EXE are always considered "binary" files and transferred accordingly. CP$ - a string which designates the communication port to be used. The values are: COM1 -- communication port 1 COM2 -- communication port 2 BPS - an integer value which indicates the baud rate of the caller. The values are: -1 = 300 bps -2 = 450 bps -3 = 1200 bps -4 = 2400 bps -5 = 4800 bps -6 = 9600 bps -7 = 19200 bps Page 66 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 APPENDIX C -- RBBS-PC in a MultiLink Environment ------------------------------------------------ RBBS-PC CPC12-5B can be run in a MultiLink Environment (i.e. IBM's PC DOS with the multi-tasking software product "MultiLink" from the Software Link, Inc.). RBBS-PC will utilize MultiLink's "enque" mechanism for file sharing (i.e. resource sharing). CONFIG's parameter 122 is how RBBS-PC knows that it will be running in a MultiLink environment. This is ESSENTIAL when running RBBS-PC under MultiLink. CONFIG allows the SYSOP to specify what MultiLink terminal type code to pass to MultiLink whenever RBBS-PC exits to DOS via a "Door". Page 15 of the MultiLink documentation specifies the various terminal type codes. When a SYSOP indicates that "doors" are available (via parameter 81 of CONFIG.BAS) and RBBS-PC is to be run under MultiLink the SYSOP is asked to select the MultiLink terminal type RBBS-PC is to inform MultiLink to expect when MultiLink is given control of the "Door." RBBS-PC CPC12-5B has been tested running two copies of RBBS-PC under DOS 2.1 and MultiLink Advanced (version 3.01) on an IBM PC which had a mother board containing 64K and an AST Comboplus board with 384K (a total of 448K). The "autoexec" file was named AUTOEXEC.BAT and contained the following parameters MLINK /9,152/9,152 It is important to avoid doing several things when running RBBS-PC under MultiLink. First NEVER RUN MLSLICE! This is because MLSLICE hangs off the PC's timer chain and the code generated by IBM's BASIC compiler violates also sorts of DOS conventions whenever it is utilizing the PC's speaker (i.e. as when RBBS-PC pages the SYSOP). In so doing, the code generated by IBM's BASIC compiler is incompatible with programs that do follow DOS conventions. Second NEVER use the DOS "PRINT" command! This is because there is a bug in the code generated by the BASIC compiler that causes the system to hang if a compiled BASIC program is running and DOS is printing something. This bug has been corrected in the BASIC compiler that was used to generate RBBS-PC.EXE that is distributed. However the version of RBBS-PC that you get (if other than from CPCUG) may not have this bug corrected. This is a bug that occurs independent of running MultiLink. Third, check your Intel 8088 chip's copyright date by opening up the cover and locating the 8088 chip. If the copyright date printed on the chip is 1978 (i.e. pre 1981), REPLACE THE INTEL 8088 CHIP!!!!! The 1978 Intel 8088 chip had several design flaws that will cause your system to occasionally lock up. One of these design flaws allowed interrupts to occur while stack switching (something that will happen running multiple partitions doing disk I/O under any multi-tasking DOS add-on such as MultiLink or even IBM's TopView). Don't blame MultiLink for the flawed Intel 8088 chip that IBM put in your PC! It costs about $70 ($35 for the chip and $35 for labor) and takes about 15 minutes to have the 1978 Intel 8088 chip replaced. Fourth, DON'T USE "BUFFERS=" in the CONFIG.SYS for DOS! This may be an "old wives tale," but I am convinced (but can't prove) that there are incompatabilities between the code the BASIC compiler generates, DOS's use of "BUFFERS=", and MultiLink. Fifth, DON'T ALLOW MNP PROTOCOL for file transfers. An incompatability exists between the Software Link, Inc.'s Multi-Link and MICROCOM's MNP software. Until the respective vendor's resolve this, don't use both Page 67 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 products concurrently! Finally, DON'T RUN PROGRAMS THAT USE THE BASIC "RUN-TIME" LIBRARY and always invoke the BASIC interperter with the command BASIC C:0! Both the BASIC interperter's handling of communications ports and BASRUN.EXE seem to violate enough DOS conventions to "lock up" MultiLink. When RBBS-PC detects that it is running in a MultiLink environment it will automatically do the following: 1. When re-cycling, it will automatically enque on the correct MultiLink resource ID for the communications port defined in CONFIG for that copy of RBBS-PC to use. 2. When re-cycling, it will automatically tell MultiLink that this is a type "9" partition (i.e. MultiLink is NOT to handle the communications port). 3. When exiting to DOS (either via the SYSOP option 7 or via a "door", RBBS-PC will automatically tell MultiLink to start handling the communications for this partition (COM1 or COM2) and what type of terminal was defined in CONFIG that would be on the communications port (MultiLink terminal types 1 through 12). It is possible to manually bring up one copy of RBBS-PC running under one of MultiLink's partition. The only way that I have been able to successfully bring up two copies of RBBS-PC (one copy running in each of two partitions) under MultiLink is to bring them up via AUTOEXE1.BAT and AUTOEXE2.BAT files. It appears, at least in 3.01 of MultiLink Advanced, that during the MultiLink initialization sequence when the partitions are being established and the "AUTOEXEx.BAT" files are being invoked that MultiLink doesn't get "confused" and lock up with a second copy of RBBS-PC present. Page 68 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 APPENDIX D -- RBBS-PC in a CORVUS Network ----------------------------------------- RBBS-PC uses the standard Corvus SEMAPHORES when sharing files among multiple copies of RBBS-PC within a Corvus Network. This is accomplished via the MS-DOS utility driver, DRIVEC2, that Corvus supplies with it's network. On a multi-server Corvus network (i.e. where there are multiple shared hard disk drives) all PC's that are running RBBS-PC within the Corvus network MUST have their "home volume" on the same server. Corvus maintains each PC's semaphores on that PC's "home volume". In order to "share" files among various PC's in a Corvus network, all the PC's that are "sharing" must also be looking at the same set of semaphores. In a single-server Corvus network this is not a consideration because there is only one "home volume." RBBS-PC has only been tested with the Corvus CONSTELLATION II interface cards and software that Corvus provides for the IBM PC. RBBS-PC should work with both Corvus' older "flat cable" network as well as their newer OMNINET twisted wire pair cable network when running CONSTELLATION II software. It is entirely possible that RBBS-PC would work with some combination of both Corvus network types as long as they were running CONSTELLATION II software. It should be self-evident that every PC within a Corvus network running RBBS-PC must have a Corvus interface card. If multiple copies of RBBS-PC are running in a Corvus network that is using older Corvus software (i.e. NOT running the CONSTELLATION II software), the interface cards must, at least, all have the CONSTELLATION II ROM. RBBS-PC is only tested to run on IBM PC's within a Corvus network. Clearly an IBM "clone" that can run IBM's DOS, RBBS-PC.EXE, and is supported by Corvus' network should also work. However, such configurations (and their infinite variations) are not part of the environment within which RBBS-PC is tested and supported. Page 69 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 APPENDIX E -- RBBS-PC in a ORCHID PCnet NETWORK or AST PCnet NETWORK -------------------------------------------------------------------- RBBS-PC CPC12-5B can be implemented on a Orchid PCnet or AST PCnet Network environment using IBM's PC DOS ver 2.x 3.x and Orchid PCnet ver 2.4c 3.0a and network interface boards or PC DOS ver 2.x 3.0 and AST PCnet Networking software ver 3.10 with their respective boards. Hardware in which this has been tested included IBM's PC,XT,AT,(PC clones). The AT was also tested at clock speeds as high as 9megs with no problems as a non-dedicated server. RBBS-PC uses non standard Orchid-AST SEMAPHORES when sharing files among multiple copies of RBBS-PC within a Orchid or AST Network. RBBS-PC calls the MS-DOS utility driver, PC-NET, that is supplied with the pcnet as a low-level function call (int 67) to lock, unlock, and loop-lock semaphore names. RBBS-PC uses the drive letter and not the drive number in the argument to specify drive of a network drive; (the server providing this drive will hold the lock). In order to get the file sharing to lock and unlock properly a few guide lines should be followed. All the system files used in RBBS-PC should use the same drive letter on the server as well as all workstations, therefore all semaphores names will be the same on all nodes. Example: if messages and users are on E:drive at the server, all the workstations (uPC's) will have to setup their network drive table so that the workstation drive e: is in fact drive e: on the server. This should all fall in place if the workstations are two floppy systems. The problem will occur if one or more of the workstations has more drives locally than two floppy drives. In that case, rearrange the drive table on the workstation in any order of drive letter, but do not skip any logical drives in the final uPC map. Tips on running RBBS-PC and PCnet 1. Server will work in dedicated or non-dedicated modes. 2. Mono Screen should be used on the server, graphics screen causes all the nodes to blink on and off as the user accesses the system files. I find that a mono screen on the server and any combination on the uPC's corrects the problem. 3. Do not use BUFFER= on the server. UPC's updates to users and messages files will be lost or over written on the system, and finally become one big mess of useless data. 4. All volumes accessed by any copy of RBBS-PC must be designated read / write because RBBS-PC uses the name function in order to determine if a file exists on all the drives in the search for a file. 5. All remote sysop activity should be done on a uPC. The server never goes back to the batch file if access in remote takes place. 6. The best system performance is achieved if PCCACHE is used on the server. All downloads and upload activity is done by the cacche. The system is fast and the hard disk heads are spared the job of keeping up with 4 users all downloading a different file at the same time. A typical download of 80k file is just 2 to 3 reads from the drive, same for uploads except it's a write of 2 or 3 times to the drive. 7. If you have the room locally, keep all the DIR.DIR and aa.dir thru zz.dir on the local volume, as well as all the menus and help files. 8. Large ram disks will improve the performance on all nodes. One such ram drive that was found to work with PCnet is TALL TREES SYSTEMS JRAM Page 70 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 and JRAM-2 boards. You will have to use the JBOOT.BIN as the first entry in the config.sys to use jram, even though PCnet said to use their drivers first in config.sys. Putting the file menus, helps, dirs, etc. in the ram disk makes the system very fast. Using the set comspec in dos 3.x is also helpful. If booting from a floppy on the network, use set comspec command (set environment) to find command.com on the ram disk. 9. The snoop key should be used with caution. If you toggle snoop on as a user is first logging on the system, you may lock up that node. Once that node is locked up all calls to the other nodes will lock up one by one. What happens is RBBS locks the message file as a user comes on the system, at the same time you are also locking the message file using the snoop on function locally. The outcome is the message file becomes locked permanently. No other node can read the message file from that point on. Page 71 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 APPENDIX F -- RBBS-PC and the Hearing Impaired ---------------------------------------------- Telecommunications Devices for the Deaf (TDD's) use the Baudot character set (i.e. 5-bit) and utilize modems that transmit at 45 baud and do not generate a carrier signal. This is primarily because such devices were initally adaptions of surplus Western Union TTY machines for telephone communications. The widespread use of Baudot devices by the hearing impaired, the previous high cost of computers and modems, and the lack of software designed for electronic communications like RBBS-PC, has impedded the change to ASCII communiations by the hearing impaired community. Unfortunately, equipment manufacturers have also made it difficult for the deaf to change. When TDD's with ASCII code transmission capability began to be offered, the majority of manufacturers limited them to only 110 baud and put disclaimers in their manuals that said ASCII was available for use but that "computer language" was "less reliable" and hard to use. Their limiting of the TDD's output screen to 12 to 20 characters further compounded the problem because the screen would overwrite several times to display one line of text from a host system. The manufacturers' "solution" to this problem was to recommend printers for communication with a host system (i.e. RBBS-PC) -- necessitating the printing out of all menus (at 110 baud!!!!). Some units now offer both 110 and 300 baud ASCII transmission in addition to the 45 baud Baudot. Unfortunately these typically only have 20 character screens. After the release of CPC12-3B in December of 1984, Ted Janossy of Rochester, Minnesota sent me a three-page letter describing the above situation. Ted's letter motivated me to test and verify the "ring-back" feature of RBBS-PC in CPC12-4A. It had not been tested in earlier versions because I had assumed (presumptiously and insensitively) that "real SYSOP's don't use ring-back RBBS-PC's." Ted's letter awakened me to the potential of RBBS-PC to facilitate communications among the hearing impaired. In the awakening I also had a chance to look down at my own feet of clay. Using option 9 of CONFIG, RBBS-PC can be configured to answer calls only after a specified number of rings (i.e. 15). The telephone companies wire the homes of the hearing impaired such that when the phone rings, the lights within the house flash on and off. With CPC12-4A a SYSOP can specify the number of rings RBBS-PC is to wait before automatically answering the phone. Setting this number high enough allows someone with a hearing impairment time enough to get to the PC running RBBS-PC. Pressing the PC's function key 5 (F5), causes RBBS-PC to immediately answer the phone. The caller would know that someone was at the keyboard because RBBS-PC answered the phone in less than the agreed upon number of rings. The caller would log on to RBBS-PC normally and the person at the PC keyboard would be able to see who it was. If the person who was called wanted to "chat" with the individual, all they would have to do would be to press function key 10 (F10). If RBBS-PC didn't answer the telephone within the agreed upon number of rings, the caller would know that whomever he was calling couldn't come to the keyboard. The caller would then log on and leave a message on RBBS-PC. I would like to thank Ted and his wife, Sue, for caring enough to show where RBBS-PC might fulfill one of it's primary purposes, "the free exchange of information," by enhancing telecommunications for the deaf. Page 72 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 APPENDIX G -- RBBS-PC and the IBM PCjr -------------------------------------- RBBS-PC adheres to the Hayes standards for autoanswer applications that are described in Chapter 9, "Writing Programs for the Smartmodem 1200," of the the SMARTMODEM 1200 HARDWARE REFERENCE MANUAL. Under the section entitled "Additional Program Considerations" Hayes recommends that autoanswer applications (like RBBS-PC) "... force the modem to answer the call (ATA) rather than allowing the modem to automatically answer...." Beginning with CPC12-5B, RBBS-PC no longer depends on the Ring Indicator signal from the modem (pin 22) in order to answer the phone (except if option 9 of CONFIG is non-zero). Here are some facts about the PCjr: 1. The PCjr's external modem interface does not have a Ring Indicator signal. 2. The PCjr requires that an external modem be opened as COM1 if no internal modem is installed. However, if no internal modem exists the PCjr requires that the COM2 RS232 registers be used even though the port has been opened as COM1. Technically this is described as using the external RS232 asynchronous adapter as logical channel 1 (i.e. COM1) but manipulating it as physical channel 2 (i.e. COM2). This occurs on a PCjr only when an internal modem is NOT present and the external RS232 interface is. 3. The 128K PCjr only provides 90K of usable RAM (the rest is used by DOS, the monitor's buffers, etc.). Fortunately PCjr owners can get up to 256K of RAM with "add-on" equipment (from IBM and others) in order to have enough RAM for RBBS-PC to run in. Here are some facts about RBBS-PC 1. CPC12-5B does not require the Ring Indicator signal in normal operation (i.e. CONFIG option 9 set to zero). 2. RBBS-PC requires 192K of RAM 3. RBBS-PC treats COM1 as if it where physical channel 1 and COM2 as if it where physical channel 2 when examining the RS232 interface's registers for carrier detect, etc. Therefore, I believe that RBBS-PC CPC12-5B would operate unmodified on a PCjr with 256K of RAM and both an internal modem (forever unused) and an external Hayes 1200 (or 100% compatable!!) modem. Several individuals have advised me that they have been able to modify RBBS-PC to run on the IBM PCjr. While none have taken the trouble to send me any .MRG or .DOC files (see section 1.4) adopting RBBS-PC to the PCjr, Steve Smith did tell me how he was able to do it for the PCjr's "internal" modem. Essentially in order to use the PCjr's "internal" modem: 1. The communication port must be opened at 300 baud, N, 8, 1 (which RBBS-PC does). 2. The modem commands for the internal modem are Ctrl N rather than the Hayes "AT" standard. Therefore the Hayes commands (i.e. string constants that begin with "AT) should be changed to Ctrl N. 3. Almost all the Hayes commands (i.e. "A" to answer the phone) are the same for the PCjr's internal modem and don't have to Page 73 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 be changed. 4. The line within RBBS-PC that tells the modem to answer the phone (line number 320 in the source code) should be changed to have the following : Ctrl N -- Modem command indicator A -- Modem command to answer the phone T 0 -- Modem command to turn transparency on so that "Ctrl N" sequences within XMODEM file transfers aren't interperted by the PCjr's internal modem as the begining of a modem command string. Since the PCjr uses interrupt X'7F' which is one of the "unused" interrupts on the other PC's in the IBM family of personal computers, Option 36 of CONFIG must be set to indicate that RBBS-PC is running on a non-IBM PC. Those with further questions about running RBBS-PC on a PCjr should contact Steve Smith directly via his voice number (301) 921-0861 or via his data number (301) 330-2784. Since all changes to RBBS-PC are "additive" (see section 1.3), anyone willing to document (via .DOC and .MRG files) how they adopted CPC12-5B to run on ALL of IBM's PC's which can run IBM's DOS can be assured such changes will be incorporated into future releases of RBBS-PC. Page 74 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 APPENDIX H -- RBBS-PC Subscription Service ------------------------------------------ It seems that many people absolutely must be on the bleeding edge of RBBS- PC and demand each new version as soon as possible after it is released. Since downloading it from my RBBS-PC ususally keeps my board busy 24 hours a day, seven days a week when each new version is released and I want my board to be used to encourage and engage in discussions, I am willing to inaugurate an additional public service in order to free up my board. Within the United States for $35 (prepaid by check or money order) you can be guaranteed next day delivery of the very NEXT release of RBBS-PC just as I mail it to the CPCUG Software Exchange. The diskettes will be sent to you directly via Federal Express's "Courier-Pak" Overnight Envelope. In case you are wondering who gets the $35 it is allocated as follows: $ 25 -- Federal Express Charge for Courier-Pak 8 -- CPCUG Software Exchange 2 -- for the hassel the family will put up with and rate changes ---- $ 35 = Total Costs Add: $ 5 for Alaska, Hawaii, and Puerto Rico $ 11 for Europe, the Far East, and Australasia Hopefully, this service will only be used by a very, VERY few! Most releases have a few fixes that get published within the first week or two that they are out. For this reason, I advise everyone to check back for fixes after a release goes out (and for the same reason I don't encourage anyone to use this "Subscription Service"). To obtain this service for the NEXT release (it does NOT apply to the current or previous releases) fill out the following form and send it along with your check or money order (no purchase orders are accepted and your canceled check is your only invoice). +--------------------------------------------------------------+ | To: D. Thomas Mack RBBS-PC Subscription Service to| | 10210 Oxfordshire Road the NEXT release of RBBS-PC (if| | Great Falls, Virginia any, and none are implied or | | 22066 promised by this offer) | |--------------------------------------------------------------| |Date Requested: Date Received: | |--------------------------------------------------------------| |To (Recipent's Name): | |--------------------------------------------------------------| |Recipent's Phone Number (required): ( ) - | |--------------------------------------------------------------| |Exact Street Address (no P.O. Box or P.O. Zip Code accepted) | | | | | |--------------------------------------------------------------| | City | State | | | | |--------------------------------------------------------------| | Signature (required) | ZIP Code for Street Address| | | | | | | +--------------------------------------------------------------+ Note: this is not a promise that there will be any new releases. Page 75 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 APPENDIX I -- RBBS-PC National Listing Service ---------------------------------------------- Frequent inquires are made about a "national" list of RBBS-PC's. In order to help SYSOP's (and potential SYSOP's) everywhere find configurations that most closely match their own, with the introduction of RBBS-PC CPC12-5B I am willing to inaugurate an additional public service and will attempt to keep an "ACCURATE" telephone listing of all publically available RBBS-PC systems. The success of this endeavor depends on you. If you would like a chance to stand up and be recognized, please fill out the following form: +--------------------------------------------------------------+ | To: Jon Martin RBBS-PC National Listing | | 4396 N. Prairie Willow Ct. Service (if any, and none is| | Concord, California implied or promised by this | | 94521 offer) | |--------------------------------------------------------------| |Please REMOVE CHANGE ADD Date Requested: | |(circle one) to your Listing. Date Action Taken: | |--------------------------------------------------------------| |SYSOP's Name: | |--------------------------------------------------------------| |DATA Phone Number (required): ( ) - | |VOICE Phone Number (optional): ( ) - | |Do NOT publish my VOICE number (please check) _____ | |--------------------------------------------------------------| |Exact Street Address (no P.O. Box or P.O. Zip Code accepted) | | | | | |--------------------------------------------------------------| | City | State | | | | |--------------------------------------------------------------| | Signature (required): | ZIP Code for Street Address| | | | | | | +--------------------------------------------------------------+ | Detailed System Information | | RBBS Name :_________________________________________| | Operating Hrs.(EST):_________________________________________| | Specialty of RBBS :_________________________________________| | Baud Rates :_________________________________________| | Number of Nodes :_________________________________________| | Modem Vendor/Model :_________________________________________| | Computer Type :_________________________________________| | Memory :_________________________________________| | Multi-Function Card:_________________________________________| | Monitor Vendor/Type:_________________________________________| | Disk Storage :_________________________________________| | Special Cards :_________________________________________| | DOS Version :_________________________________________| | Other Software |_________________________________________| |--------------------------------------------------------------| | Additional information/comments: | | | | | | | | | | Feel free to include a photo of yourself if you would like so| | that we can get to know our fellow SYSOPS. | +--------------------------------------------------------------+ Page 76 of 77 RBBS-PC CPC12-5B, Copyright 1985 by D. Thomas Mack August 25, 1985 APPENDIX J -- RBBS-PC and The Ark-Paradyne Modem Switch Settings ---------------------------------------------------------------- The following are the switch and jumper settings for the Modem. Switch 1 UUUDDUUD (Where U = Up = On and D = Down = Off ) Switch 2 UDDDDUDD Briefly these settings use Hayes Mode, ROM, Switch 3 DUUDUUUU 2400 Baud,8,N,1, and auto answer disabled. MODEM DTE/CLOCK FLOW BUSY DTR JUMPERS E8-E9 E15-E16 E4-E7 E11-E14 Use "2400 for option 38 "Modem rate" in CONFIG.EXE. The ARK modem has two modes, ARK and HAYES. The zap or modem reset "ATZ" or "Z" command requires a "CONFIRM Y/N" and therefore cannot be used by RBBS. The HAYES mode works well for RBBS and the ARK mode works best with PC- TALK, QMODEM, EXECPCT, etc. Do to incomplete compatability to the HAYES 2400 (i.e. lack of time delay from MCR to DTR to drop of Carrier) the ARK Modem can't use the following RBBS functions: Doors, Remote Sysop to DOS, and the RBBS version of MNP Protocol. The following LED lights should be "ON" while waiting for a call: TALK ANS AA PWR DTR RTS If the AA light is not "ON", check the 2nd line of RBBSxPC.DEF for the modem string starting with ATM0Q1 etc. The string should have S0=1. The Ark modem requires that option 9 of CONFIG to be set to 0. =========== E N D O F CPC12-5B D O C U M E N T A T I O N ========== Page 77 of 77